I am wondering because I searched the pdf "[noSql] the definitive guide" and "beginning [noSql]" for the word "inheritance" but I didn't find anything? am I missing something? because I'm doing a tablePerHierarchy inheritance with hibernate and mysql, does that become deprecated for some reason in [noSql]?
(replace [noSql] with the "not only sql" database you like)
Well it's a pretty old question, but since I ended up here I'd like to add a 2017 update.
If your using mongoose to connect to MongoDb you may want to check out discriminators:
Documentation was a little bit vague for me at first, this article could be a better place to grasp the idea.
I know this answer is a little late, but for MongoDB, you're probably looking at something slightly different.
Mongo is schemaless, so the concept of "tablePerHierarchy" is not necessarily useful.
Assume the following
In an RDMS you would probably have something like this
But MongoDB does not have a schema. So you do not need to structure data in this way. Instead, you would have a "collection" containing all objects (or "documents") of type A or B (or C...).
So your collection would be a series of objects like this:
You'll notice that I'm storing objects of type A right beside objects of type B. MongoDB makes this very easy. Just pull up a Document from the Collection and it "magically" has all of the appropriate fields/properties.
However, if you have "data objects" or "entities", you can make your life easier by adding a type.
This makes it easier to write a factory class for loading your objects.