From: Sam Smoot <ssmoot@...>
Date: 2007-03-22T10:15:08+09:00
Subject: Re: Object/Relational Mapping is the Vietnam of Computer Science

On Mar 21, 5:34 pm, Robert Klemme <shortcut...@googlemail.com> wrote:
> On 21.03.2007 23:22, SamSmootwrote:
>
> > Ok. I can stand the SQL love-in no longer. :)
>
> > Anyone who's actually used db4o:
>
> > * Knows it's a perfectly viable solution for the majority of
> > applications out today as they don't approach it's limits performance,
> > or storage wise
> > * Knows it's a simpler database to develop for than generating reams
> > of mapping files or accepting the limitations of a system like
> > ActiveRecord
> > * Knows the *data* is safe because the database is open-source,
> > exports *very* easily, and no one is about to timebomb the frameworks
> > * Knows that for many common scenarios the performance will wipe the
> > floor with many popular RDBMS's
>
> How does it do schema migration?  Do you have experience with that?
>
> Kind regards
>
>         robert

My experience with it was in the 4.x line, but I managed it then much
like I do now. If I want to export some data from MySQL, I don't
typically use a sql dump. I drop into irb, and write 3 or 4 lines
using ActiveRecord and FasterCSV. :)

You can replicate with db4o, or I imagine now that they have an
administrative GUI you could probably dump the data through that.

Or do you mean class migrations? To the best of my recollection, that
was one of the advantages of db4o, automatic versioning without any of
the hoops some of the other vendors made you jump through. Don't quote
me on that, but I'm fairly certain there was no assembly/module
registration.