Thanks for the info, I had the same problem and was able to fix it by
renaming my relation to not override the other one and turning off
allow_override. Removing allow_column_override would help eliminate
the confusion since replacing the column makes the relation not work
without the undocumented _actual_foreign_key_column you mentioned.
Regards,
-TH
> allow_column_override is not used for this, its used to entirely
> obliterate the knowledge of the underlying Column so that you can
> place a relation() there instead. Its also deprecated since the same
> effect can be acheived with "exclude_columns" (thanks for reminding me
> so i can remove it from 0.5).
>
> Since you dont want to obliterate the column and you actually need it,
> do this:
>
> mapper(Class, mytable, properties={
> '_actual_foreign_key_column' : mytable.c.sensor,
> 'sensor':relation(Sensor)
>
>
>
> })
>
> > mapper(Sensor, sensor)
> > detectionmapper = mapper(Detection, detection,
> > allow_column_override= True , properties={
> > 'sensor' : relation(Sensor),
> > })
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
