[
https://issues.apache.org/jira/browse/OPENJPA-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432582#comment-17432582
]
ASF subversion and git services commented on OPENJPA-2883:
----------------------------------------------------------
Commit eae49816f471e3ae657b4eff4528b1a0284e2ce5 in openjpa's branch
refs/heads/OPENJPA-2883 from Maxim Solodovnik
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=eae4981 ]
[OPENJPA-2883] 'supportsAutoAssign' is turned OFF when
'useTriggersForAutoAssign' is ON
> UseTriggersForAutoAssign in Oracle seems to be broken
> -----------------------------------------------------
>
> Key: OPENJPA-2883
> URL: https://issues.apache.org/jira/browse/OPENJPA-2883
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 3.2.0
> Reporter: Maxim Solodovnik
> Assignee: Maxim Solodovnik
> Priority: Major
> Fix For: 3.2.1
>
>
> Everything works as expected in {{openjpa:3.1.2}}
> In case Oracle DB is used and Entity has {{@GeneratedValue(strategy =
> GenerationType.IDENTITY)}} annotation
> The following error is thrown:
> {code}
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: ORA-32795:
> cannot insert into a generated always identity column
> {stmnt 2049051802 CREATE OR REPLACE TRIGGER PObjectNative_id_TRG BEFORE
> INSERT ON PObjectNative FOR EACH ROW BEGIN SELECT
> PObjectNative_id_SEQ.nextval INTO :new.id FROM DUAL; END
> PObjectNative_id_TRG;} [code=32795, state=99999]
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:58)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConnectionDecorator.java:955)
> at
> org.apache.openjpa.lib.jdbc.DelegatingStatement.executeUpdate(DelegatingStatement.java:123)
> at
> org.apache.openjpa.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:1375)
> at
> org.apache.openjpa.jdbc.schema.SchemaTool.createTable(SchemaTool.java:1114)
> at
> org.apache.openjpa.jdbc.schema.SchemaTool.buildSchema(SchemaTool.java:660)
> at org.apache.openjpa.jdbc.schema.SchemaTool.add(SchemaTool.java:565)
> at org.apache.openjpa.jdbc.schema.SchemaTool.add(SchemaTool.java:400)
> at org.apache.openjpa.jdbc.schema.SchemaTool.run(SchemaTool.java:372)
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:571)
> ... 36 more
> {code}
> The issue seems to be caused by introducing {{"GENERATED ALWAYS AS
> IDENTITY"}} in {{3.2.0}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
