Hi, I did some more investigation about this subject and found the source for this problem and perhaps some hints for people willing to help out with this problem:
Around line 1002 of mapper.py there is a call to prop = self.columntoproperty[column] Why this fails? It seems because two different ID columns seem to be confused by the mapper. On the first look both columns seem equal: (Pdb) >>> self.columntoproperty.keys()[-16] Column(u'ID',PGInteger(),primary_key=True,nullable=False,default=PassiveDefault(<sqlalchemy.sql._TextClause object at 0xb75733cc>)) >>> column Column(u'ID',PGInteger(),primary_key=True,nullable=False,default=PassiveDefault(<sqlalchemy.sql._TextClause object at 0xb7572a8c>)) Second look shows that they are different ones: (Pdb) >> self.columntoproperty.keys()[-16].default.arg.text 'nextval((\'"download_id_seq"\'::text)::regclass)' >> column.default.arg.text 'nextval((\'myschema."downloadtopic_id_seq"\'::text)::regclass)' Why does this happen? Why does the mapper try to match the ID column from DownloadTopic table to the Download table? ... and how can I avoid that? Thx for your any hints! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
