[Nitro] Og in legacy environments
kevwil at gmail.com
Tue Aug 16 11:15:40 EDT 2005
On 8/16/05, Robert Wagner <robbie.wilhelm at gmail.com> wrote:
> hi kevin,
> currently only primary key and foreign key aliases are supported.
> set_primary_key :name, :foreign_field
> sequence aliases will come soon :)
> george calls it the reverse mode.
> look at: http://nitrohq.com/view/Release_notes
> i think, to make og real powerful, there has to be done a few things in this
> direction. the concept of og is not to care at all at the db ddl. let
> og do all the
> work. in practice, i would say, that is simply impossible. fourther more, there
> are many legacy apps that could be enhanced by ruby og scripts if it was the
> 'swiss knife' of OR libs.
> what i'd like to see is a way to read the properties/
> relationdeclares/ foreign-key
> stuff per ogified class from an external file, that is quick to parse
> like ini or yaml (NOT xml). i was pretty convinced once i saw, how
> helma (http://helma.org/) handled that stuff with ini files. so i'm
> doing so with a php OR class and i'm quite happy with it.
> that could be quite useful to generate ddl from that files and vica versa....
> just a few thoughts.
> 2005/8/16, Kevin Williams <kevwil at gmail.com>:
> > I'm having trouble with primary keys and sequences in a legacy DB.
> > There seems to be a naming convention tha Og expects, something like
> > "oid" for the primary key, "<tablename>_oid" for foreign keys, and
> > "<tablename>_oid_seq" for sequences.
> > How do I override these names to match an existing database?
> > _______________________________________________
> > Nitro-general mailing list
> > Nitro-general at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/nitro-general
> Nitro-general mailing list
> Nitro-general at rubyforge.org
More information about the Nitro-general