[Treebase-devel] hibernate_sequence takes charge in treebasedev

[Vladimir G. <vga...@ne...>]

As of late afternoon Fri Jan 22, all tables in treebase- 
dev.nescent.org/treebasedev draw their PK ids from hibernate_sequence,  
which was updated to start with 16000000000.

Running 'mvn test' seemingly hangs forever on  
org.cipres.treebase.service.matrix.MatrixServiceImplTest.  This might  
be due to an intrinsic problem with the test, or maybe because the  
test's transaction bumped into someone else's transaction?  [I did  
manage to run this test successfully individually earlier in the day,  
but that time only 3 tables were switched to hibernate_sequence.]

I see a couple that could be done to verify success:
  - Check that unit tests now execute correctly (Youjun?)
  - Check that data entry operations from UI work (Bill?)


A few more remarks:

  - Repeating the sequence re-targeting procedure on another db  
instance will take me about an hour (there is manual work  
involved).    It's not too bad, but still means we should perform it  
on all instances as soon as treebasedev is confirmed to function  
correctly.

  - The huge starting number for hibernate_sequence is probably due to  
tests.  This suggests we should never run tests on the production  
instance.

  - All sequences but hibernate_sequence can now be dropped, I think.