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
The Public Knowledge Project Support Forum is moving to

This forum will be maintained permanently as an archived historical resource, but all new questions should be added to the new forum. Questions will no longer be monitored on this old forum after March 30, 2015.

suggestion to make oracle compatability a reality

Postby » 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: No registered users and 2 guests