Rudman, I have just finished submitting patches to add Derby and DB2 support. I suggest you start working off the Roller_2.0 branch in SVN instead of 1.x. I have already made fixes to shorten all of the constraint/index names to less or equal to 18 characters. You can see my patches [1] and do the same. Email them here, then Dave will review and merge them into the branch. If you need to change the table name, I'd advise to also add to the migration script SQL to create the new table, move the data and drop the old table for other databases. Make sure that you add to the build.xml to generate the oracle folder and defaults (commented out) for the hibernate.cfg.xml and I think there's one other file as well. That's all I can think of right now.
Regards, Elias [1] http://torrez.us/2005/08/23/roller/patches/ Question to team: I'm being lazy right now and don't remember what's the difference between the UpgradeDatabase code and the migration scripts. Is it duplicate work? or does UpgradeDatabase uses the migration scripts? On 9/14/05, Rudman Max <[EMAIL PROTECTED]> wrote: > 2.0 really would be a great time -- especially that it requires > 'comment' table to be renamed. Let me know what to do... > > Max > > On Sep 13, 2005, at 10:42 PM, Allen Gilliland wrote: > > > yes! we want it! > > > > with 2.0 coming up this would be a great time to hammer out Oracle > > support. this would also align nicely with some of the db changes > > that Elias has been working on to get Derby and DB2 supported. > > > > i'm not sure what the best submission method is though ... Dave? > > > > -- Allen > > > > > > Rudman Max wrote: > > > > > >> We have Roller 1.x running against Oracle 10g database. Migration > >> was pretty painless as I recall except these major issues: > >> > >> 1) Manual query in the RefererManager had to be reworked (or more > >> precisely an 'if' for Oracle created) > >> 2) Some constraint names were too long > >> 3) 'comment' table name conflicted with an Oracle keyword. > >> > >> Let me know if the project has interest in Oracle support and > >> what the process is for submitting these kinds of patches. > >> > >> Max > > > >
