[
https://issues.apache.org/jira/browse/OPENJPA-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-1946.
--------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: MySQLDictionary maps timestamps to
DATETIME (lines 131 and 279; it already did in 2006, so the reporter's
TIMESTAMP likely came from a custom definition), and MySQL 8 defaults
explicit_defaults_for_timestamp=ON, so TIMESTAMP columns are nullable without
an implicit default. Please reopen if this still happens with OpenJPA 4.x.
> TemporalType.TIMESTAMP creates a non-nullable column on MySQL.
> --------------------------------------------------------------
>
> Key: OPENJPA-1946
> URL: https://issues.apache.org/jira/browse/OPENJPA-1946
> Project: OpenJPA
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.0.1
> Environment: MySQL 5
> Reporter: Milosz Tylenda
> Priority: Minor
>
> TemporalType.TIMESTAMP creates a non-nullable column with a default value on
> MySQL whereas on other databases a nullable column is created. The issue was
> reported on user's mailing list [1].
> [1]
> http://openjpa.208410.n2.nabble.com/MappingTool-generated-SQL-for-TIMESTAMP-tp5858072p5858072.html
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
