I have limited time (as we all do I'm sure) and I want to embed my database into my distribution so my research led me to Ozone OODBMS .
Has anyone here worked with Ozone OODBMS (or any oodbms for that matter) and/or have any thoughts about this product? The concept of an oodbms really struck a cord with me and mapping my model to a relational database doesn't appeal to me at all (if only for the amount of code I would have to write). I'm expecting my application will only have 1-2k objects in storage on average (3-4k on the high end) at any given time.
I've read some articles discussing the positives/negatives of an oodbms but I can't tell if the negatives are because the general theory behind the concept is flawed (doubt it) or if the technology just hasn't matured yet and/or general resistance to a non-relational database (more likely).
Thanks and Happy Holidays! Bill
Increasingly, people seem to misinterpret complexity as sophistication, which is baffling - the incomprehensible should cause suspicion rather than admiration. Possibly this trend results from a mistaken belief that using a somewhat mysterious device confers an aura of power on the user. Niklaus Wirth