Main Overview Wiki Issues Forum Build Fisheye
Issue Details (XML | Word | Printable)

Key: CMP-920
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Shay Banon
Reporter: Kenny MacLeod
Votes: 0
Watchers: 0

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

Allow identifiers to be externalised

Created: 08/Jan/10 09:25 AM   Updated: 08/Jan/10 09:25 AM
Component/s: Compass::Core
Affects Version/s: 2.2.0 GA
Fix Version/s: None

 Description  « Hide
I would very much like to see the ability to externalise identifiers from the entities being persisted in a compass index. For example:

compassSession.create(myObject, id);

This would be an alternative to the ID field(s) being mapped to a property of the object being persisted.

The use case would be in situations where the identifiers are not a property of the objects, either because the class model is a legacy model which does not contain the identifiers, or because the class model contains only naturals keys, and we want to use surrogate keys instead.

Under the covers, this wouldn't seem to be a big change to how Compass works. The ID would be stored as a lucene field, as it is now, but wouldn't be reconsituted back into the object when retrieve from the index.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.