175 is working for me. It has "alter sequence .. cache", and it reads the
tables built with 171. It's only 176 which doesn't like the tables.
On Wednesday, May 28, 2014 6:28:59 PM UTC-7, Brian Craft wrote:
>
> With much digging through the archives, I found this example for setting
> the sequen
With much digging through the archives, I found this example for setting
the sequence when creating a table:
CREATE SEQUENCE TESTSEQ;
CREATE TABLE TEST(ID INT DEFAULT NEXT VALUE FOR TESTSEQ PRIMARY KEY);
However I still have no migration strategy due to the problems moving from
171 to 176.
On
Checking if I can change the sequence cache by updating the
information_schema table, in 171. Doesn't seem to work:
update information_schema.sequences set cache = 2001 where
sequence_name='SYSTEM_SEQUENCE_91459F04_54A2_41A6_8BA7_FF4BBFF4EFBD'
throws this error:
JdbcSQLException Feature not su
I updated from 1.3.171 to 1.3.176 to pick up the "alter sequence .. cache"
command. After changing the cache, on the next start of the app h2 is
unable to connect to the db. It fills the trace file with this:
05-28 17:27:33 database: ALTER TABLE PUBLIC.PROBES ADD CONSTRAINT
PUBLIC.CONSTRAINT_8D
