[h2] Avoiding corruptions in frequent unclean-shutdown scenario

[Germano Rizzo]

Hi all,
 we're about to implement a project that uses H2 on board of some RFID 
readers, for a steel factory. The database will be used to store RFID 
readings, so we will write few datas relatively often (2 records/second, 
maybe).

Problem is, being an "embedded" scenario, the readers will usually go down 
without a proper, clean shutdown, at a frequency of 3-4 times per day. 
There's really no way to avoid the possibility that the power-off happens 
during a write.

OS is Linux, with a proper journaled filesystem (EXT4) stored on a micro-sd 
card; CPU is an Atom processor. Supplier assures me that as far as the 
operating system is concerned, this scenario is O.K.

Which is the best way to avoid corruptions of H2, detect them and recover 
from them, in a programmatical way? No user interaction should be required.

In particular:

- Which url parameters should we use? is LOG=2 enough?
- Which version should we use? 172, nightly, wait for the next one? Project 
will be rolled out at 20 of july.
- Will it make any difference if I create indexes? Does them increase the 
"exposed area" for corruptions?
- Which is the worst-case scenario for this? I'm ok losing the last few 
writes.

Thanks a lot,

   Germano

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [h2] Unique index or primary key violation: "SYS_ID ON PUBLIC.SYS(ID)" [23505-168] (using 1.3.168)

[Germano Rizzo]

Same problem here. I can add that my application is widely deployed, and 
each instance created a db for its internal configuration. Now everyone of 
them is failing, so I think it's not a problem of corruption... maybe the 
start parameters? The jdbc url with which it was created is: 

jdbc:h2://amp_db;LOCK_MODE=0;UNDO_LOG=0;TRACE_LEVEL_FILE=0;FILE_LOCK=SOCKET;AUTO_SERVER=TRUE
 


You can find a failing db here: 

https://www.dropbox.com/s/h0i9ys98dz5xp88/amp_db.h2.zip

Opening it with version 1.3.176 will give the error. Latest 1.4.* version 
doesn't.

Please advise here. I can't upgrade if this is not solved somehow... 
anyhow, thanks for the excellent work you're doing! 

   Germano 

Il giorno giovedì 10 aprile 2014 12:11:22 UTC+2, Joerg Z. ha scritto:
>
> Hi,
> same problem here.
> After upgrade h2-1.3.174.jar to h2-1.3.176.jar and connect to my exist db 
> file I get to following trace: (without any executed statement, just 
> connect)
>
> 04-10 11:50:39 database: ALTER TABLE PUBLIC.REL_USERS_RIGHTS ADD 
> CONSTRAINT PUBLIC.REL_USERS_RIGHTS_FK_ID_USER FOREIGN KEY(ID_USER) 
> REFERENCES PUBLIC.TBL_USERS(ID) NOCHECK
> org.h2.jdbc.JdbcSQLException: Eindeutiger Index oder Primärschlüssel 
> verletzt: "PRIMARY KEY ON .PAGE_INDEX"
> Unique index or primary key violation: "PRIMARY KEY ON .PAGE_INDEX"; 
> SQL statement:
> ALTER TABLE PUBLIC.REL_USERS_RIGHTS ADD CONSTRAINT 
> PUBLIC.REL_USERS_RIGHTS_FK_ID_USER FOREIGN KEY(ID_USER) REFERENCES 
> PUBLIC.TBL_USERS(ID) NOCHECK [23505-176]
>
> A post repair with 
> backup/restore
>  doesn't 
> help and run into same issue.
> Regards,
> Joerg
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Re: [h2] Unique index or primary key violation: "SYS_ID ON PUBLIC.SYS(ID)" [23505-168] (using 1.3.168)

[Germano Rizzo]

Hi Thomas,
so your opinion is that all the db's are corrupted? The strange 
thing is, they fail to open only with the latest stable version. Every 
other version I tried works fine, and this configuration have worked in 40 
installations for 3 years now, across different versions of H2. Do you want 
me to start another thread?

 Germano

Il giorno martedì 6 maggio 2014 07:59:45 UTC+2, Thomas Mueller ha scritto:
>
> Hi,
>
> If you are using LOCK_MODE=0;UNDO_LOG=0 then you need to be aware of the 
> risks. See the FAQ and the documentation.
>
> Please use different email subjects for different problems.
>
> Regards,
> Thomas
>
>
> On Monday, May 5, 2014, mano > wrote:
>
>> mano wrote
>> > Opening it with version 1.3.168 will give the error.
>>
>> Sorry, I meant 1.3.176.
>>
>>
>>
>>
>> --
>> View this message in context: 
>> http://h2-database.66688.n3.nabble.com/Unique-index-or-primary-key-violation-SYS-ID-ON-PUBLIC-SYS-ID-23505-168-using-1-3-168-tp4028700p4029078.html
>> Sent from the H2 Database mailing list archive at Nabble.com.
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "H2 Database" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to h2-database+unsubscr...@googlegroups.com.
>> To post to this group, send email to h2-database@googlegroups.com.
>> Visit this group at http://groups.google.com/group/h2-database.
>> For more options, visit https://groups.google.com/d/optout.
>>
> 

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

[h2] Corruption in a database created in 1.3.174 when opening and closing it in 1.3.176

[Germano Rizzo]

Hi,
   I have a reproducible bug with versions 174 and 176 (at least). A db 
created with 1.3.174 (no particular settings) corrupts when just opening 
and closing it in 1.3.176. To reproduce:


   1. download this sql (generated by the SCRIPT command from a test db of 
   mine): https://www.dropbox.com/s/gjng7vfqkpp9fio/SQL.sql
   2. create a blank db in 1.3.174 and restore the script; close the db
   3. open the db in 1.3.176, close it;
   4. reopen the db in 1.3.176. it will crash.
   
As said, I don't use any parameter for the JDBC URL. The crash is this:

Exception in thread "main" org.h2.jdbc.JdbcSQLException: Unique index or 
primary key violation: "PRIMARY KEY ON .PAGE_INDEX"; SQL statement:
ALTER TABLE PUBLIC.DETAILS ADD CONSTRAINT PUBLIC.FK_DETAILS FOREIGN KEY(ID) 
REFERENCES PUBLIC.ENTITIES(ID) NOCHECK [23505-176]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
at org.h2.message.DbException.get(DbException.java:178)
at org.h2.message.DbException.get(DbException.java:154)
at 
org.h2.index.PageDataIndex.getNewDuplicateKeyException(PageDataIndex.java:166)
at org.h2.index.PageDataIndex.add(PageDataIndex.java:144)
at org.h2.store.PageStore.addMeta(PageStore.java:1808)
...

Here you can find the corrupted db: 
https://www.dropbox.com/s/e4fj39jaoqwsdom/test.h2.db

You can use SquirrelSQL to test, or use this eclipse project: 
https://www.dropbox.com/s/ez2lre6t7uf64vc/H2Bug.7z

To use it:

   1. Put only h2-1.3.174.jar in the path
   2. Launch DBCreate174.java
   3. Put only h2-1.3.176.jar in the path
   4. Launch DBTriggerBug176.java
   5. crash
   
Hope this helps. Let me know if I can be of further assistance.

  Germano



-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

[h2] Re: Corruption in a database created in 1.3.174 when opening and closing it in 1.3.176

[Germano Rizzo]

Actually, in the eclipse project the URL has also 
";TRACE_LEVEL_FILE=0;FILE_LOCK=FS;". If you remove it (leaving no url 
parameter), the bug triggers the same.

Il giorno venerdì 9 maggio 2014 15:30:07 UTC+2, Germano Rizzo ha scritto:
>
> Hi,
>I have a reproducible bug with versions 174 and 176 (at least). A db 
> created with 1.3.174 (no particular settings) corrupts when just opening 
> and closing it in 1.3.176. To reproduce:
>
>
>1. download this sql (generated by the SCRIPT command from a test db 
>of mine): https://www.dropbox.com/s/gjng7vfqkpp9fio/SQL.sql
>2. create a blank db in 1.3.174 and restore the script; close the db
>3. open the db in 1.3.176, close it;
>4. reopen the db in 1.3.176. it will crash.
>
> As said, I don't use any parameter for the JDBC URL. The crash is this:
>
> Exception in thread "main" org.h2.jdbc.JdbcSQLException: Unique index or 
> primary key violation: "PRIMARY KEY ON """".PAGE_INDEX"; SQL statement:
> ALTER TABLE PUBLIC.DETAILS ADD CONSTRAINT PUBLIC.FK_DETAILS FOREIGN 
> KEY(ID) REFERENCES PUBLIC.ENTITIES(ID) NOCHECK [23505-176]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
> at org.h2.message.DbException.get(DbException.java:178)
> at org.h2.message.DbException.get(DbException.java:154)
> at 
> org.h2.index.PageDataIndex.getNewDuplicateKeyException(PageDataIndex.java:166)
> at org.h2.index.PageDataIndex.add(PageDataIndex.java:144)
> at org.h2.store.PageStore.addMeta(PageStore.java:1808)
> ...
>
> Here you can find the corrupted db: 
> https://www.dropbox.com/s/e4fj39jaoqwsdom/test.h2.db
>
> You can use SquirrelSQL to test, or use this eclipse project: 
> https://www.dropbox.com/s/ez2lre6t7uf64vc/H2Bug.7z
>
> To use it:
>
>1. Put only h2-1.3.174.jar in the path
>2. Launch DBCreate174.java
>3. Put only h2-1.3.176.jar in the path
>4. Launch DBTriggerBug176.java
>5. crash
>
> Hope this helps. Let me know if I can be of further assistance.
>
>   Germano
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

[h2] Re: Corruption in a database created in 1.3.174 when opening and closing it in 1.3.176

[Germano Rizzo]

If I remove the foreign key definition (last line in the SQL) the problem 
doesn't present itself.

Of course I can't do this, as I have many databases already created. I'll 
stick with 174 until this is solved.

Il giorno venerdì 9 maggio 2014 15:30:07 UTC+2, Germano Rizzo ha scritto:
>
> Hi,
>I have a reproducible bug with versions 174 and 176 (at least). A db 
> created with 1.3.174 (no particular settings) corrupts when just opening 
> and closing it in 1.3.176. To reproduce:
>
>
>1. download this sql (generated by the SCRIPT command from a test db 
>of mine): https://www.dropbox.com/s/gjng7vfqkpp9fio/SQL.sql
>2. create a blank db in 1.3.174 and restore the script; close the db
>3. open the db in 1.3.176, close it;
>4. reopen the db in 1.3.176. it will crash.
>
> As said, I don't use any parameter for the JDBC URL. The crash is this:
>
> Exception in thread "main" org.h2.jdbc.JdbcSQLException: Unique index or 
> primary key violation: "PRIMARY KEY ON """".PAGE_INDEX"; SQL statement:
> ALTER TABLE PUBLIC.DETAILS ADD CONSTRAINT PUBLIC.FK_DETAILS FOREIGN 
> KEY(ID) REFERENCES PUBLIC.ENTITIES(ID) NOCHECK [23505-176]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
> at org.h2.message.DbException.get(DbException.java:178)
> at org.h2.message.DbException.get(DbException.java:154)
> at 
> org.h2.index.PageDataIndex.getNewDuplicateKeyException(PageDataIndex.java:166)
> at org.h2.index.PageDataIndex.add(PageDataIndex.java:144)
> at org.h2.store.PageStore.addMeta(PageStore.java:1808)
> ...
>
> Here you can find the corrupted db: 
> https://www.dropbox.com/s/e4fj39jaoqwsdom/test.h2.db
>
> You can use SquirrelSQL to test, or use this eclipse project: 
> https://www.dropbox.com/s/ez2lre6t7uf64vc/H2Bug.7z
>
> To use it:
>
>1. Put only h2-1.3.174.jar in the path
>2. Launch DBCreate174.java
>3. Put only h2-1.3.176.jar in the path
>4. Launch DBTriggerBug176.java
>5. crash
>
> Hope this helps. Let me know if I can be of further assistance.
>
>   Germano
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Re: [h2] Unique index or primary key violation: "SYS_ID ON PUBLIC.SYS(ID)" [23505-168] (using 1.3.168)

[Germano Rizzo]

Provided 
here<https://groups.google.com/forum/?hl=it#!topic/h2-database/lNp80bgbvBY>. 
Thanks!

Il giorno giovedì 22 maggio 2014 17:43:18 UTC+2, Thomas Mueller ha scritto:
>
> Hi
>
> I would need a reproducible test case, or the database file. 
>
> Regards, Thomas 
>
> On Thursday, May 22, 2014, jack jin > 
> wrote:
>
>> when I upgrade to 1.3.176,I have the same problem.  the old version h2 is 
>> works fine with the db file
>>
>> On Tuesday, May 6, 2014 5:00:52 PM UTC+8, Germano Rizzo wrote:
>>>
>>> Hi Thomas,
>>> so your opinion is that all the db's are corrupted? The strange 
>>> thing is, they fail to open only with the latest stable version. Every 
>>> other version I tried works fine, and this configuration have worked in 40 
>>> installations for 3 years now, across different versions of H2. Do you want 
>>> me to start another thread?
>>>
>>>  Germano
>>>
>>> Il giorno martedì 6 maggio 2014 07:59:45 UTC+2, Thomas Mueller ha 
>>> scritto:
>>>>
>>>> Hi,
>>>>
>>>> If you are using LOCK_MODE=0;UNDO_LOG=0 then you need to be aware of 
>>>> the risks. See the FAQ and the documentation.
>>>>
>>>> Please use different email subjects for different problems.
>>>>
>>>> Regards,
>>>> Thomas
>>>>
>>>>
>>>> On Monday, May 5, 2014, mano  wrote:
>>>>
>>>>> mano wrote
>>>>> > Opening it with version 1.3.168 will give the error.
>>>>>
>>>>> Sorry, I meant 1.3.176.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context: http://h2-database.66688.n3.
>>>>> nabble.com/Unique-index-or-primary-key-violation-SYS-ID-
>>>>> ON-PUBLIC-SYS-ID-23505-168-using-1-3-168-tp4028700p4029078.html
>>>>> Sent from the H2 Database mailing list archive at Nabble.com.
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "H2 Database" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to h2-database+unsubscr...@googlegroups.com.
>>>>> To post to this group, send email to h2-database@googlegroups.com.
>>>>> Visit this group at http://groups.google.com/group/h2-database.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>   -- 
>> You received this message because you are subscribed to the Google Groups 
>> "H2 Database" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to h2-database+unsubscr...@googlegroups.com.
>> To post to this group, send email to h2-database@googlegroups.com.
>> Visit this group at http://groups.google.com/group/h2-database.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Re: [h2] Re: Corruption in a database created in 1.3.174 when opening and closing it in 1.3.176

[Germano Rizzo]

Thank you, I hope you'll manage to fix this. Let me know if I can be of 
some help. Let me add that:

- version 175 seems to behave like 174, so the problem seems to be between 
175 and 176.

- the latest 2 beta versions seem to be ok

Thanks,

  Germano

Il giorno giovedì 22 maggio 2014 21:46:54 UTC+2, Thomas Mueller ha scritto:
>
> Hi,
>
> Thanks a lot for the test case! I could reproduce the problem now. The 
> SQL.sql can be reduced to:
>
> create table a(x int primary key); 
> create table b(x int, y int, primary key(x, y));
> alter table b add foreign key(x) references a(x);
>
> I used the following shell script to reproduce the error:
>
> rm testdb*
> rm empty.sql
> touch empty.sql
> java -cp h2-1.3.174.jar org.h2.tools.RunScript -url jdbc:h2:./testdb 
> -script SQL.sql -user x
> java -cp h2-1.3.176.jar org.h2.tools.RunScript -url jdbc:h2:./testdb 
> -script empty.sql -user x
> java -cp h2-1.3.176.jar org.h2.tools.RunScript -url jdbc:h2:./testdb 
> -script empty.sql -user x
>
> I'm not sure yet what the problem is, but it looks like it's related to 
> bugfixes for contraints (see the change log).
>
> Regards,
> Thomas
>
>
>
>
>
> On Fri, May 16, 2014 at 11:57 AM, Niko Paltzer 
> > wrote:
>
>> I can confirm the problem. We tried to move from 1.3.172 to 1.3.174 and 
>> got the same error.
>>
>>
>>
>>
>> On Friday, May 9, 2014 4:12:29 PM UTC+2, Germano Rizzo wrote:
>>>
>>> If I remove the foreign key definition (last line in the SQL) the 
>>> problem doesn't present itself.
>>>
>>> Of course I can't do this, as I have many databases already created. 
>>> I'll stick with 174 until this is solved.
>>>
>>> Il giorno venerdì 9 maggio 2014 15:30:07 UTC+2, Germano Rizzo ha scritto:
>>>>
>>>> Hi,
>>>>I have a reproducible bug with versions 174 and 176 (at least). A db 
>>>> created with 1.3.174 (no particular settings) corrupts when just opening 
>>>> and closing it in 1.3.176. To reproduce:
>>>>
>>>>
>>>>1. download this sql (generated by the SCRIPT command from a test 
>>>>db of mine): https://www.dropbox.com/s/gjng7vfqkpp9fio/SQL.sql
>>>>2. create a blank db in 1.3.174 and restore the script; close the db
>>>>3. open the db in 1.3.176, close it;
>>>>4. reopen the db in 1.3.176. it will crash.
>>>>
>>>> As said, I don't use any parameter for the JDBC URL. The crash is this:
>>>>
>>>> Exception in thread "main" org.h2.jdbc.JdbcSQLException: Unique index 
>>>> or primary key violation: "PRIMARY KEY ON """".PAGE_INDEX"; SQL statement:
>>>> ALTER TABLE PUBLIC.DETAILS ADD CONSTRAINT PUBLIC.FK_DETAILS FOREIGN 
>>>> KEY(ID) REFERENCES PUBLIC.ENTITIES(ID) NOCHECK [23505-176]
>>>> at org.h2.message.DbException.getJdbcSQLException(
>>>> DbException.java:344)
>>>> at org.h2.message.DbException.get(DbException.java:178)
>>>> at org.h2.message.DbException.get(DbException.java:154)
>>>> at org.h2.index.PageDataIndex.getNewDuplicateKeyException(
>>>> PageDataIndex.java:166)
>>>> at org.h2.index.PageDataIndex.add(PageDataIndex.java:144)
>>>> at org.h2.store.PageStore.addMeta(PageStore.java:1808)
>>>> ...
>>>>
>>>> Here you can find the corrupted db: https://www.dropbox.com/s/
>>>> e4fj39jaoqwsdom/test.h2.db
>>>>
>>>> You can use SquirrelSQL to test, or use this eclipse project: 
>>>> https://www.dropbox.com/s/ez2lre6t7uf64vc/H2Bug.7z
>>>>
>>>> To use it:
>>>>
>>>>1. Put only h2-1.3.174.jar in the path
>>>>2. Launch DBCreate174.java
>>>>3. Put only h2-1.3.176.jar in the path
>>>>4. Launch DBTriggerBug176.java
>>>>5. crash
>>>>
>>>> Hope this helps. Let me know if I can be of further assistance.
>>>>
>>>>   Germano
>>>>
>>>>
>>>>
>>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "H2 Database" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to h2-database...@googlegroups.com .
>> To post to this group, send email to h2-da...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/h2-database.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Re: [h2] Corruption in a database created in 1.3.174 when opening and closing it in 1.3.176

[Germano Rizzo]

Great work, Thomas, thank you.

Will I be able to open a database created with 174, and never opened in 
176, with the new version?

Thanks again,

Germano

Il giorno lunedì 2 giugno 2014 18:04:13 UTC+2, Thomas Mueller ha scritto:
>
> Hi,
>
> Yes, this problem was introduced in version 1.3.176, actually by fixing 
> another bug. It happens when upgrading a database with a special kind of 
> foreign key constraint from an older version to 1.3.176. I found the 
> problem now and have a fix for it. I will need to release a new version; a 
> workaround is to stay with the older version, or upgrade to the newer 
> version by first converting to a SQL script and then creating a new 
> database.
>
> Regards,
> Thomas
>
>
>
> On Mon, Jun 2, 2014 at 2:04 PM, Cecil Westerhof  
> wrote:
>
>> 2014-06-01 10:16 GMT+02:00 Cecil Westerhof :
>>
>>> 2014-05-09 15:30 GMT+02:00 Germano Rizzo :
>>>
>>>>I have a reproducible bug with versions 174 and 176 (at least). A db 
>>>> created with 1.3.174 (no particular settings) corrupts when just opening 
>>>> and closing it in 1.3.176. To reproduce:
>>>>
>>>
>>> ​I have also a problem with 176. With at least one (but not all) 
>>> database I get the following error when opening the database in H2 console:
>>> Unique index or primary key violation: "PRIMARY KEY ON """".PAGE_INDEX"; 
>>> SQL statement:
>>> ALTER TABLE PUBLIC.WEIGHTS ADD CONSTRAINT PUBLIC.CONSTRAINT_74 FOREIGN 
>>> KEY(CATEGORYID) REFERENCES PUBLIC.CATEGORIES(ID) NOCHECK [23505-176] 
>>> <http://127.0.0.2:8082/login.do?jsessionid=906bcb32b9beddff983be35575c2bd82#>
>>>  
>>> 23505/23505
>>>
>>> When going back to 174 luckily all my databases work like before.
>>>
>>> weights is defined as:
>>> FIELD   
>>> <http://127.0.0.2:8082/query.do?jsessionid=3f87e6740013f7de2ee326159fb984e7#>
>>> TYPE   
>>> <http://127.0.0.2:8082/query.do?jsessionid=3f87e6740013f7de2ee326159fb984e7#>
>>>  
>>> NULL   
>>> <http://127.0.0.2:8082/query.do?jsessionid=3f87e6740013f7de2ee326159fb984e7#>
>>> KEY   
>>> <http://127.0.0.2:8082/query.do?jsessionid=3f87e6740013f7de2ee326159fb984e7#>
>>>  
>>> DEFAULT   
>>> <http://127.0.0.2:8082/query.do?jsessionid=3f87e6740013f7de2ee326159fb984e7#>
>>> CATEGORYIDUUID(2147483647) NOPRINULLMEASUREDATEDATE(8)NOPRI
>>> CURRENT_DATE()WEIGHTDOUBLE(17)NONULLFAT DOUBLE(17)YESNULLWATERDOUBLE(17)
>>> YESNULLMUSCLEDOUBLE(17)YESNULL 
>>> When certain information is needed: let me know.
>>>
>>
>> ​I just gone to 175. That works also. So the bug was introduced in 176.
>>
>> -- 
>> Cecil Westerhof 
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "H2 Database" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to h2-database+unsubscr...@googlegroups.com.
>> To post to this group, send email to h2-database@googlegroups.com.
>> Visit this group at http://groups.google.com/group/h2-database.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.