Re: [Treebase-devel] Hibernate_sequence need a bigger value

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

On Dec 25, 2009, at 8:42 AM, William Piel wrote:

> One of the early bugs after the DB2->Pg migration was that new  
> records generated an uncaught exception because sequences had not  
> been setup -- so Rutger went through an added sequence definitions  
> for various tables. It's not impossible that sequences were added  
> some for tables where Hibernate was already taking care of this,  
> causing a clash.

Bill, have new studies been entered into the DB after Rutger created  
the sequences?

My reason for asking: The tables for which Youjun encountered the  
problem in unit tests (taxonlabel and phylotreenode) are among the  
ones, I'd guess, that get multiple new rows with a new study.  I'd  
then expect that submitting a new study would have produced the same  
error Youjun has encountered.  If it had not, it could indicate that  
the tests use a data access method not used by the main code.

--Vladimir