[Nitro] Og and legacy tables

[Jonathan Buch]

Hi,

> It might also allow Nitro to leverage ActiveRecord::Migration for
> managing database upgrades and rollbacks.

This is one of the first things always asked by new people who come
 from AR to #nitro.  Migrations.  I always tell them, that Og doesn't
have those, partly because of a different mindset:  Og tells, how the
result should look like, and adapts the DB accordingly, not the other
way round.

This is just one side of course, there may as well be a need for real
migrations in Og, but who's going to implement that.  We can't even get
that shite testing mess fixed which G introduced.

> (Of course, it's possible these features are already possible with Og
> and this is simply an exercise in public humility, but there's value in
> that too...)

There's never a too dumb question.  :)  This merely shows that there are
areas in Og which are unknown to the general public and only accessable
to people like me who read the source over and over again.  Nothing to
be ashamed of, really.

Jo

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/