[h2] Re: 1.3.172 vs 1.4.199

2019-07-17 Thread Patrice
Thank you so much. It's working now.
I think I need the 1.4.199 version because in my user program h2 I have 
several threads that concurently access the database to modify it.

Le mercredi 17 juillet 2019 13:38:29 UTC+2, Patrice a écrit :
>
> I have a database managed under h2 1.3.172. I wanted to update with 
> version 1.4.199.
> I make a simple SELECT on a table, I disconnect and when reconnecting I 
> get the following error:
> *Single index violation or primary key: "PRIMARY KEY ON" "" ".PAGE_INDEX"*
> *Unique index or primary key violation: "PRIMARY KEY ON" "" ".PAGE_INDEX"; 
> SQL statement:*
> *ALTER TABLE PUBLIC.LIMES ADD CONSTRAINT PUBLIC.FK_POINT1 FOREIGN KEY 
> (ID_PREMIER_POINT) REFERENCES PUBLIC.POINTS (ID) NOCHECK [23505-199] 
> 23505/23505 (Help)*
> These same actions in version 1.3.172 do not create any errors.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/3dbe5b38-1676-4de0-aed9-f3ce9ee56743%40googlegroups.com.


Re: [h2] Re: 1.3.172 vs 1.4.199

2019-07-17 Thread Patrice Henrio
Thank you so much. It's working now.
I think I need the 1.4.199 version because in my user program h2 I have
several threads that concurently access the database to modify it.

Le mer. 17 juil. 2019 à 15:03, Evgenij Ryazanov  a écrit :

> Hello.
>
> Your version is very old. Automatic upgrade is not always clean.
>
> You need to export your database to SQL with a
> SCRIPT TO 'filename.sql'
> command using 1.3.172.
>
> After in you can create a new database with 1.4.199 and execute
> RUNSCRIPT FROM 'filename.sql'
> to populate it with your data.
>
> See also
> https://h2database.com/html/tutorial.html#upgrade_backup_restore
>
> Note that 1.4.199 uses another storage engine by default, it allows
> concurrent access from multiple threads and transactions, but it isn't as
> mature as an old engine. However, you can still use the old storage engine
> if you wish.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/h2-database/677cdf81-c547-4e63-8cac-4e70891b1613%40googlegroups.com
> 
> .
>


-- 
Si vous vous intéressez à l'histoire, vous pouvez parcourir mon site :
http://histoiremondiale.net
ou si cette première adresse ne fonctionne pas (maintenance du serveur par
exemple) sur http://histoiremondiale.free.fr



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/CAMxFFkMqPLGFtYve2bxcK7AHyS_RHwyMsNrCFxgwfF8jtd8tZQ%40mail.gmail.com.


[h2] Re: 1.3.172 vs 1.4.199

2019-07-17 Thread Evgenij Ryazanov
Hello.

Your version is very old. Automatic upgrade is not always clean.

You need to export your database to SQL with a
SCRIPT TO 'filename.sql'
command using 1.3.172.

After in you can create a new database with 1.4.199 and execute
RUNSCRIPT FROM 'filename.sql'
to populate it with your data.

See also
https://h2database.com/html/tutorial.html#upgrade_backup_restore

Note that 1.4.199 uses another storage engine by default, it allows 
concurrent access from multiple threads and transactions, but it isn't as 
mature as an old engine. However, you can still use the old storage engine 
if you wish.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/677cdf81-c547-4e63-8cac-4e70891b1613%40googlegroups.com.