Heh. Very much not.
My current "design braindump" includes the following features:
in reply to Re: Any NoSQL equivalents of an ORM?
in thread Any NoSQL equivalents of an ORM?
In short I'm really tackling the sort of problems that an ORM on top of a relational database makes easy.
- Create and maintain schemas for complex objects.
- Maintain bidirectional object relationships. (Think master-child relationships - from the master you should be able to find the children, and each child needs to know its master. This should be automatically maintained.)
- Ability to dump networks of related objects.
- Ability to load them elsewhere.
- A conflict resolution algorithm in case two different clients updated an object at the same time without seeing what the other was doing.