A composite type would be perfect for me.
> Michael Bayer wrote:
> > you cant do it right now. but its something we could support. its
> > unclear to me if we should just go for "composite types" as the way to
> > do it, or just use a callable. using a composite is likely cleaner
> > and would integrate with the "save" process better (otherwise, the
> > callable needs to generate the "discriminator" value at save time as
> > well).
>
> > On Dec 3, 2007, at 11:09 AM, Koen Bok wrote:
>
> >> I'd like to make a polymorphic mapper based on two columns. Is that
> >> possible?
>
> >> See example code here:http://paste.pocoo.org/show/13799/
>
> >> Thanks, Koen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---