[Treebase-devel] Logistics for TB2 ID generation, 2nd attempt

[Vladimir G. <vla...@du...>]

I am still figuring out, in consultation with Xianhua here, how to  
instruct Hibernate to do what we want, but it is clear we need back a  
DB instance with individual sequences.  The most expedient way would  
be to just re-create it from a backup.

So, does anyone object to dropping the current treebasedev instance  
(that's the one connected to 6666 as well as treebase-dev.nescent.org  
front-ends)?  Just in case, we will preserve a recent backup. (Would  
one from yesterday or the day before suffice?)

If that's ok, I'll ask Jon to empty treebasedev, and re-create from  
the same Dec 8 backup he used for treebasestage. Depending on whether  
Jon has extra space, this might cause a few hours of downtime.

--Vladimir


On Jan 29, 2010, at 11:28 AM, Rutger Vos wrote:

>> All this speaks in favor of the theory that TB2 Hibernate got  
>> confused
>> by the DB2-->Postgres switch, which was done in the hope that
>> Hibernate default behavior would remain the same.    It appears we
>> must now figure out how to explicitly instruct TB2 DAO and Hibernate
>> to behave in the way that best matches their behavior back in the DB2
>> days.
>
> Right, and that behaviour would be that the database itself
> autoincrements IDs without intervention from hibernate, as the DB2
> creation commands indicate.