Ticket #669 (closed Enhancement: fixed)
Core: redesign Property API
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.4 |
Component: | DeepaMehta Standard Distribution | Version: | 4.3 |
Keywords: | Cc: | dgf, Malte, carolina | |
Complexity: | 3 | Area: | Application Framework / API |
Module: | deepamehta-core |
Description
Topic/Association? properties should be accessible without obtaining the Topic/Association? object in advance. The Topic/Association? ID should be sufficient.
This is required in conjunction with #668 (and thus #592). Furthermore it improves performance.
Change History
comment:2 Changed 10 years ago by Jörg Richter
Get property w/o fetching the object first (#669).
The DeepaMehtaService has 2 new methods:
Object getProperty(long id, String propUri) boolean hasProperty(long id, String propUri)
They access a Topic/Association? property without obtaining the Topic/Association? object in advance.
The id is a Topic ID or an Association ID.
BREAKING CHANGES
The DeepaMehtaStorage interface has changed, so storage layer implementations must be adapted.
The Neo4j based implementation is adapted.
See #669.