> -----Original Message----- > From: Aur�lien Pernoud [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 11, 2002 10:26 AM > To: Jetspeed Users List > Subject: Re: Migrating from 1.4b1 to 1.4b2 : if you have trouble with > old database (users/profiles) > > > > ----- Original Message ----- > From: "David Sean Taylor" <[EMAIL PROTECTED]> > > > > In 1.4b1, Hypersonic used the ID_TABLE to gen new ids. > > In 1.4b2, it uses the native method to gen new ids to be consistent with > all > > databases supported by jetspeed. > > Hypersonic's native method is to use an auto-increment column. > > > > Unfortunately I don't have a good solution (yet). > > You will need to reseed Hypersonic's id generator to be of a > higher value > > than the ids that are already in your system. > > I haven't figured out a way to do this short of writing Java code. > > > > For a quick fix, change your security-schema.xml back to using the > ID_TABLE, > > add the new column, and regenerate. > > You must then add the new column to your hypersonic database in > production > > by edition jetspeed.script. > > > > Finally, I don't think that the default Hypersonic DB is a good > choice for > a > > production system. > > It basically persists SQL statements to a text file, and stores > the db in > > memory during runtime. > > Have you looked at MySQL? > > Oups, forgot to tell, I'm using Oracle... And I have the exception when > creating new user, but it worked fine to get old users profile, > by altering > the existing turbine_user table and adding the "CHANGED_DATE" column > > Did I did something wrong ? Did you succesfully migrate your existing > users/psml from 1.4b1 to 1.4b2 ? > > Cause under Oracle I also had the ID_TABLE in 1.4b1, and it seemed to be > use. > > Aurelien > PS : sorry for the double mail, fucking outlook express at home > didn't like > the "reply" button ! > Yes, it appears that my response went back to you only.
With 1.4b2, Oracle uses sequences. I looked at the 1.4b1 release, and it appears to me that it was using sequences too, so I don't know why you have it configured for the ID_TABLE with Oracle. If you are using the ID_TABLE, I suggest switching to sequences since obviously this is much more robust. To convert your system, its simple, just reseed the Oracle sequence: CREATE SEQUENCE TURBINE_USER_SEQ INCREMENT BY 1 START WITH 1000 NOMAXVALUE NOCYCLE NOCACHE ORDER; ............................................................^ set higher than your highest id, which you can find by SELECT MAX(USER_ID) FORM TURBINE_USER; You will then need to alter the table to use the sequence and the new column added in 1.4b2 Regards, David -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
