On Feb 7, 2008, at 1:33 PM, Richard Levasseur wrote:
For the syntax of it, I'd go for something like
`child_obj.change_from(parent_obj)` or `child_obj =
ChildClass.create_from(parent_obj)`, perhaps implicitly invoked when
you do child_obj.type = parent_obj. Not sure about that last part,
On Feb 6, 7:01 pm, Michael Bayer [EMAIL PROTECTED] wrote:
we dont yet support a seamless change of inheriting type. your best
bet is to issue the SQL to the table directly which changes the
polymorphic value to the new value, then inserting/deleting from the
child tables as needed..then
I am very pleased to announce that version 0.5.1 of Elixir
(http://elixir.ematia.de) is now available. As always, feedback is
very welcome, preferably on Elixir mailing list.
This is mostly a bug fixes release (especially for people using
inheritance), but we have also a few minor new features,
I have a self referential hierarchy structure in a table that I have
mapped with SA 0.4. What I would like to do is query the table given a
node, and find its grandchildren based on some criteria in both the
child and grandchildren nodes. In SQL I would do:
SELECT * FROM nodehierarchy AS
Ok, so I've been looking into getting it to work when the child record
doesn't exist. I haven't had much luck.
I wrote a stub mapper extension for translate_row and
populate_instance, but it doesn't seem to be called when it goes to
fetch the information for the child row.
mapper(Parent,
