Taking Neo4j as an example, I think the only strategy mappable in a meaningful way is SEQUENCE. While Neo4j doesn't have native sequences, they can sufficiently well be emulated using specific nodes maintaining the sequence values.
So when using TABLE or IDENTITY with Neo4j, I think we should raise an exception. Instead, we currently fall back to the one and only implemented strategy which also stores the "table name" as a label ("hibernate_sequences in the case of SEQUENCE) which doesn't not really seem right and requires us to maintain one query (for obtaining the next value) per sequence, whereas actually one query would suffice (see {{Neo4jSequenceGenerator}}) ) if this label wouldn't exist.
|
