----- 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 ! -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
