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 <cldwester...@gmail.com>
> wrote:
>
>> 2014-06-01 10:16 GMT+02:00 Cecil Westerhof <cldwester...@gmail.com>:
>>
>>> 2014-05-09 15:30 GMT+02:00 Germano Rizzo <germano.ri...@gmail.com>:
>>>
>>>> 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.
