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
On May 15, 2008, at 3:23 PM, Chris Guin wrote:
> My goal is to have a one-to-many relation defined using the same
> name as the foreign key column underneath. So that, if my
> "Detection" table has a foreignkey column named "sensor," the
> following mappers should work, I think:
allow_col
