[ https://forge.continuent.org/jira/browse/SEQUOIA-842?page=all ]
Emmanuel Cecchet closed SEQUOIA-842:
------------------------------------
Resolution: Won't Fix
This is a PosgreSQL specific issue that cannot be fixed in Sequoia (no database
dependent code).
As sequences are in fact handled as stored procedures in PostgreSQL, you should
use the standard {call nextval(...)} JDBC call instead.
You can find information related to this in the documentation at
http://sequoia.continuent.org/doc/2.10/userGuide/ar01s06.html#using_sequence_with_hibernate
If you need support for 'select nextval()' calls, you should use our p/cluster
commercial product that has a specific parser for PostgreSQL sequences.
> Sequence are not synchronized
> -----------------------------
>
> Key: SEQUOIA-842
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-842
> Project: Sequoia
> Type: Bug
> Components: Core
> Versions: Sequoia 3.0 beta1
> Environment: Linux Red Hat Enterprise Linux AS release 4 (Nahant Update 2)
> Postgres 8.1.4
> Reporter: Vincent Moreau
> Assignee: Emmanuel Cecchet
>
>
> select nextval('test_seq') from JDBC is only executed on one backend and
> therefore the sequences current values are not the same on the 2 databases
> bakends :
> After some select nextval from JDBC, here is what I have on the 2 PostgreSQL
> backends :
> BACKEND ONE :
> test=# select nextval('test_seq');
> nextval
> ---------
> 86
> (1 row)
> BACKEND TWO :
> test=# select nextval('test_seq');
> nextval
> ---------
> 1
> (1 row)
> Cheers,
> Vincent
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
