Thanks for being so helpful - that particular issue appears to be smoothed out now.
Chris At 02:03 PM 4/3/2008, you wrote: >On Apr 3, 2008, at 1:43 PM, Michael Bayer wrote: > > > > > > > the opposite. polymorphic_on should only be set on the Event mapper, > > and there should not be a discriminator column on the "detection" > > table. The base "event" table needs to determine the type in all > > cases. The reason for this is because when rows come in for the Event > > mapper, it only knows about the "event.discriminator" column - it has > > no knowledge that some partcular subclasses should be looking at a > > different column. I'll add an assertion case for this now. > > > >eh not that simple re: the assertion case. There's more exotic >situations where the "polymorphic_on" is described individually for >each mapper, although these are "read only" discriminators. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
