[
https://issues.apache.org/jira/browse/JDO-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated JDO-782:
-----------------------------
Description:
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 OracleAdaptern
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)
was: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.
> Initially deferred constraint should be r%moved 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)
