On May 3, 2007, at 2:41 PM, shday wrote:
>
> The problem seems to be related to a backref I had. I found a way
> without using backref and now things work.
>
> With this I get a unicode error:
> acc_mapper =
> mapper(ACCProtocolSpecies,acc_protocol_species_table,properties=
> {'models':relation
> (Model,secondary=model_acc_protocol_table,lazy=False,backref='acc_prot
> ocols'),
>
> 'study_requests':relation
> (StudyRequest,secondary=model_acc_protocol_table,lazy=False)})
> With this I don't:
> acc_mapper =
> mapper(ACCProtocolSpecies,acc_protocol_species_table,properties=
> {'models':relation
> (Model,secondary=model_acc_protocol_table,lazy=False),
>
> 'study_requests':relation
> (StudyRequest,secondary=model_acc_protocol_table,lazy=False)})
>
Ok well thats a bug in SA. what is the specific join condition to
the model_acc_protocol_table / primary keys in the related tables ?
'color' and 'acc_protocol_id' are foreign key columns in the
association table (and are part of how the relationship joins ?) a
stack trace here would tell me the bug is where i think it is (my
guess is, dependency.py line 383).
I also notice you have the same table used as a "secondary" table in
two different relationships which also might create confusion but not
related to unicode.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
