They are supposed to be better than an RDMS as a model of real-world things like motor cars where an object (like a washer) can be an entity in its own right and an essential part of several other objects (like engine and gearbox). You can represent a physical object as an object rather than as a set of normalized tables. They don't seem to be used for raw data-processing databases and they are slow.
I think if you study Java you might get an idea of how an object oriented database might work. Here is a small example showing how people can be considered both an object and being the most common object in a particular class. While people could be considered part of the animal class or life class it is not very practicle unless you are a biologist.
OK. The Top of the class is People. Then you create addittional classes which will be subclasses of people like Staff, Faculty, Consultants, visitors, vendors, contractors. Since they are all people you could just say list all people. Or I could say list all contracors. Or I might say list all people who are faculty and staff. I might not need to know the table names. Java is a very interesting programming language and I guess you would have to actually learn it and use it to understand how it works and what its advantages and disadvantages are.
Some databases or applications use things similar to this. For instance you could have files or tables that have the same key and are co-files of each other. If you have some kind of way to keep track that they are cofiles, then you dont have to say this key equals that because you know they are cofiles or of the same class.
If you do not like my post feel free to point out your opinion or my errors.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.