I had a similar problem to this and solved it by renaming teh foreign key field. So in your case you might try something like "Project.customer" instead of "Project.CustomerID".
SQLObject tries to do some magic in there when matching the id fields to objects, and sometimes you can confuse it.
actually is not magic, it's right there on the docs it creates an id col for each ref, whatI believe is actually happening here is that your being overlap by that one and since python (sadly doesn't checks for redefining instance variables basically because there is no way to know of the variable is new or just changing the value the "error" passes thru)
There's also a way to specify the name of the ID column in your model, but I can't remember how off the top of my head.
you will need to speficy it in the sqlmeta, the way to use it is
class Customer(SQLObject)
class sqlmeta:
the correct value I don't remenber but it's on the sqlmeta docs.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---
