DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Key: NUCCORE-1023
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
DataNucleus Core

Move creation of FlushProcess to store plugins, since they know what they can handle in terms of referential integrity etc

Created: 30/Mar/13 02:51 PM   Updated: 06/Apr/13 09:59 AM   Resolved: 30/Mar/13 03:28 PM
Component/s: Code Structure
Affects Version/s: None
Fix Version/s: 3.2.2

 Description  « Hide
Ultimately we want to have a FlushProcess for RDBMS that decides if an object of a class can be persisted without any impact on other classes (due to FKs). The RDBMS plugin is the only thing that knows whether a class will have a FK or not (ok, the metadata sub-system knows if there is a relation field or inheritance, but doesn't know if there is an external FK). Best way is to let the XXXStoreManager be responsible for choosing its own FlushProcess (whilst still providing some standard ones as now)

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 30/Mar/13 03:28 PM
SVN trunk now passes control of the FlushProcess to the store plugin