[
https://issues.apache.org/jira/browse/OPENJPA-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Parkerson updated OPENJPA-2196:
-------------------------------------
Attachment: OPENJPA-2196-2.2.0.patch
This patch works around the case where the ALTER SEQUENCE statement fails to
execute (which will happen on PostgreSQL if the sequence is not owned by the
current connection's user). A warning message is logged for each sequence
indicating that the sequence was not modified and that sequence values are not
cached.
> Create Sequence Postgres 9.1
> ----------------------------
>
> Key: OPENJPA-2196
> URL: https://issues.apache.org/jira/browse/OPENJPA-2196
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc, jpa
> Affects Versions: 2.2.0
> Environment: OpenJPA-2.2.0
> Transaction-type JTA
> Postgres 9.1
> JBoss 6.1
> Reporter: Hendi Marcos Ramos Silva
> Assignee: Albert Lee
> Fix For: 2.2.1
>
> Attachments: OPENJPA-2196-2.2.0.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Sorry my bad english ..
> when annotated a entity with @SequenceGenerator and with allocationSize = 1
> and initialValue = 1, the method DBDictionary.commonCreateAlterSequenceSQL is
> creating a alter sequence sql invalid for Postgres 9.1.
> Despite the documentation of postgres inform you that the other parameters
> are optional
> (http://www.postgresql.org/docs/9.1/static/sql-altersequence.html), an error
> occurs in executing the sql below.
> Eg: ALTER SEQUENCE schema_experimento.usuario_sq (no other attributes)
> Even the method NativeJDBCSeq.udpateSql being fault tolerant, the connection
> is marked for rollback and not allowing run the next val of sequence.
> Hêndi Marcos
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
