object-oriented-database

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. I am looking for an object database for Python (no handmade pickles :D). What are my options (besides the obvious ZODB )? MongoDB perhaps comes close - not object oriented but document-oriented and coming close to object databases. mikez302 Dobbin . Somewhat similar to ZODB, but much simpler. It looks nice but I haven't tried it myself. I haven't been able to find much information about it. It has been at version 0.2 for

I am evaluating two object databases, db4o ( http://www.db4o.com ) and Eloquera Database ( http://eloquera.com ) for a coming project. I have to choose one. My basic requirement is scalability, multi user support and easy type evolution for RAD. Please share your real world experience. If you have both, can you compare these two? Which do you prefer? For the last 2 years I've been using DB4O, and I'm now switching to Eloquera. My reasons, in order: I'm building a commercial product, and the royalty based licensing on DB4O is WAY to high; DB4O said we could "talk about it", but I'm a very small

I thought it was about time to have a look at OO databases and decided to use db4o for my next little project - a small library. Consider the following objects: Book, Category. A Book can be in 0-n categories and a Category can be applied to 0-m Books. My first thought is to have a joining object such as BookCatecory but after a bit of Googling I see that this is not appropriate for 'Real OO'. So another approach (recommended by many) is to have a list in both objects: Book.categories and Category.books. One side handles the relationship: Book.addCategory adds Category to Book.categories and

I don't know if this is the right title for this question. Anyway, recently I have heard about that you could make life easier when creating database. By in which you use object based database. It will make migration to other type of database also easier e.g. from MySQL to SQLlite or something else. Anyway the main way I do a webpage with database access now is that I manually write down the Query to fetch what I need from a database. However it can be done in some other way also which does not involve I have to write query. I want to know how this other method work. How to search it in Google

I'm a very beginner on DB designing and I need to create a DB for a project. I can explain what I wanna do in Object Oriented terms and thankfully a DB expert would be kind enough to explain me how I can deal with this in a DB aspect . I wanna create a User (Id, Name) entity that would have a relation with a Location entity (state, city). So in programming language i would like to have the following class User { String Name; Int Id; Location location; } class Location { String State; String City; } Could someone explain me how I can deal with this? It depends on your project requirements

I have read this post: http://jenkins-ci.org/content/summary-report-git-repository-disruption-incident-nov-10th which describes an incident where a user accidentally triggered a git push --force from an outdated state of the repository. Now of course this requires some clean up to restore the original state branches. But since Git never deletes information as I understand this clean up process is always possible. So even though you rebase, push --force (and other operations that might rewrite the history) the original commits are still there they just needs to be found right? In short are the

I'm playing around with db4o, and I have the Object Manager viewer thingy for Visual Studio. It seems okay, but not exactly on par with tools like HeidiSQL/SQL Studio/etc., not to mention that it locks the db4o file--I can't use my db4o app and Object Manager at the same time. Maybe I'm using it wrong, but regardless, I'd like to know what else is out there. What tools would you recommend for looking at and manipulating db4o files? UPDATE: I've been using LINQPad. There is some yak-shaving involved, but it's working pretty well. It still leaves a lot to be desired in terms of the functionality

That's the question. Give only one reason you think why have OODB failed or why many systems nowadays still use relational databases. Can we answer more than once? Another reason is that relational DB's have a strong foundation in mathematics: from the definition of a relation, right through to the normal forms, the theory is rock solid. It is true that the relational model does not map well to OO, but IMHO the benefits and stability of that model outweigh the mapping problem. Phil Bennett The main reason is SQL. It is very useful to be able to use the data from a database in other contexts

Quite a while ago, I heard about Object databases. Cool concept and all. Now, with the event of ORMs everywhere, does anyone still use any of the Object oriented Databases systems? Are they relevant? Are they practical? ConcernedOfTunbridgeWells OO databases never got out of a niche market. They are good for some applications - where the data structure lends itself to being represented by an object graph - but never held the compelling advantage over a RDBMS to cross the chasm. The key advantage touted for OODBMS products is the tight integration to the host language - there is no object