Hi Emmanuel,

SINGLE_TABLE is probably not ideal as Datomic as namespacing the attribute name by some property of the entity is equivalent, but faster and more compact. It certainly is supported, however.

Going back and evaluating, it looks like TABLE_PER_CLASS is actually natural for EAV stores. Originally, I thought that inherited properties were included in the set of properties on the PersistentClass definition, which problematized resolving a property upon retrieval in a tuple snapshot. While there are legitimate uses for joined inheritance (it allows Datomic to function as a graph database more effectively), it's not necessary for now.

I think this issue can be closed.

Thanks!