You are viewing the PKP Support Forum | PKP Home Wiki

suggestion to make oracle compatability a reality

Are you an Editor, Author, or Journal Manager in need of help? Want to talk to us about workflow issues? This is your forum.

Moderators: jmacgreg, michael, vgabler, John

Forum rules
This forum is meant for general questions about the usability of OJS from an everyday user's perspective: journal managers, authors, and editors are welcome to post questions here, as are librarians and other support staff. We welcome general questions about the role of OJS and how the workflow works, as well as specific function- or user-related questions.

What to do if you have general, workflow or usability questions about OJS:

1. Read the documentation. We've written documentation to cover from OJS basics to system administration and code development, and we encourage you to read it.

2. take a look at the tutorials. We will continue to add tutorials covering OJS basics as time goes on.

3. Post a question. Questions are always welcome here, but if it's a technical question you should probably post to the OJS Technical Support subforum; if you have a development question, try the OJS Development subforum.

suggestion to make oracle compatability a reality

Postby smcphillips@nla.gov.au » Thu Jul 14, 2005 11:15 pm

Hi guys,

Looks like a great system you've got here. I haven't played much with it yet, as I've been trying to get oracle integration happening.

The main stumbling block I'm coming across is Oracle's object name length limit. MySQL's is 64 characters (I think), while Oracle's is 30. This includes column, table, sequence, index and trigger names.

I appreciate this problably isn't much of a priority for you, but if a future version of ojs refactored its db object naming system to the lower threshold of 30 characters, oracle integration could be a viable option.

Return to OJS Editorial Support and Discussion

Who is online

Users browsing this forum: Google [Bot] and 3 guests