[
https://issues.apache.org/jira/browse/JDO-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044795#comment-17044795
]
Craig L Russell edited comment on JDO-782 at 2/25/20 8:11 PM:
--------------------------------------------------------------
DataNucleus is the reference implementation for JDO. The Apache JDO project
deals with the specification, API, and TCK.
This issue is related to DataNucleus, not the JDO project. Please file a report
with DataNucleus.
[http://www.datanucleus.org/documentation/problem_reporting.html]
was (Author: clr):
This issue is related to DataNucleus, not the JDO project. Please file a bug
report with DataNucleus.
[http://www.datanucleus.org/documentation/problem_reporting.html]
> Initially deferred constraint should be removed from BaseDatastoreAdapter
> instead of child classes
> --------------------------------------------------------------------------------------------------
>
> Key: JDO-782
> URL: https://issues.apache.org/jira/browse/JDO-782
> Project: JDO
> Issue Type: Improvement
> Reporter: László Bodor
> Priority: Major
>
> It seems like only Oracle supports initially deferred constraints, so it
> would make sense to remove it from BaseDatastoreAdapter instead of removing
> it from every single subclass, and adding it only to OracleAdapter.
> My original issue was that Datanucleus generated initially deferred
> constraints for MariaDB because it used BaseDatastoreAdapter. However, maybe
> it makes sense to create a MariaDbAdapter (which inherits from Mysql), there
> is another way to fix that (proposed above)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
