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)

Type: Improvement Improvement
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 Store Neo4j

Cache Node with ObjectProvider to cut down on lookups

Created: 03/Aug/12 10:54 AM   Updated: 09/Aug/12 08:58 AM   Resolved: 03/Aug/12 10:55 AM
Component/s: Persistence, Query
Affects Version/s: None
Fix Version/s: 3.1.0.release

 Description  « Hide
Whenever a user operation requires the lookup of a Node for an ObjectProvider this results in a Cypher query to get the Node (or db.getNodeById()). Obviously each lookup will cost, so we can store the Node in the ObjectProvider "associatedValues".

May possibly need some further treatment later if during the lifecycle an ObjectProvider is attempted to be used with a different GraphDatabaseService but we'll approach that when the time comes - raise JIRA for it if some exception is thrown relating to Node invalid for the GraphDatabaseService

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 03/Aug/12 10:55 AM
SVN trunk does this now