I was recently reading Rob Conery's post about DB4O and it was very interesting. My question is really concerned with class generation and future use of Subsonic and DB4O.
As Subsonic looks at the database and then generates classes how would this work for DB4O. Would the classes have to be written by hand and then DB4O would store the objects as defined by the class or would there be some database design procedure that a class generator like Subsonic could use?
Will Subsonic include DB4O as one of the databases it works against in future builds?
Would the classes have to be written by hand and then DB4O would store the objects as defined by the class or would there be some database design procedure that a class generator like Subsonic could use?
With either SubSonic or DB4O, you can write your classes by hand. In fact, this is a pretty normal way to do things. Once you've created your classes by hand, SubSonic can generate relational database tables. DB4O doesn't need relational database tables, so there is no value add to SubSonic at that point.
Will Subsonic include DB4O as one of the databases it works against in future builds?
That doesn't make sense. DB4O is an object-oriented database. There is no relational mapping needed. SubSonic is an object-relational mapping tool and therefore it's only relevant for relational databases.
SubSonic has no use in the DB4O world.