You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Maxim Solodovnik (Jira)" <ji...@apache.org> on 2022/09/15 04:27:00 UTC

[jira] [Resolved] (OPENJPA-2902) H2 database v.2.1.210 create table failed cause [Dictionary - autoAssignClause]

     [ https://issues.apache.org/jira/browse/OPENJPA-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik resolved OPENJPA-2902.
---------------------------------------
    Fix Version/s:     (was: 3.2.3)
       Resolution: Abandoned

PR was closed, the issue seems to be NREP :(

> H2 database v.2.1.210 create table failed cause [Dictionary - autoAssignClause]
> -------------------------------------------------------------------------------
>
>                 Key: OPENJPA-2902
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2902
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 3.2.2
>            Reporter: bo
>            Priority: Blocker
>
> "IDENTITY" is a deprecated H2-specific syntax, it can be used only in {{REGULAR}} (default) and {{LEGACY}} compatibility modes.
> It isn't valid in {{STRICT}} mode and in all compatibility modes for other database systems.
> We can use standard-compliant {{GENERATED BY DEFAULT AS IDENTITY}} in all compatibility modes. Some compatibility modes also provide support for various additional vendor-specific declarations, more details in their documentation:
> [https://h2database.com/html/features.html#compatibility]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)