Subsonic and DB4O

I was recently reading Rob Conery's post about DB4开发者_C百科O 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.

---

The only place i can see for Subsonic in this technology stack would be to use Subsonic to replicate (instead of/in addition to NHibernate) a db4o database to some RDBMS.

See: http://www.db4o.com/about/productinformation/drs/

It makes more sense for db4o to latch on to Subsonic to do RDBMS persistance then it is for Subonic to use db4o to generate/re-use classes. A db4o file does not contain a fully qualified domain schema. It could thus be possible that a db4o domain has some unpersisted types that can never be discovered by a tool such as Subsonic because no object of that type has ever been written to the database.