#787: SQLObject missing table.q.field mappings for ForeignKey columns.
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: anonymous
Type: defect | Status: closed
Priority: normal | Milestone:
Component: SQLObject | Version: 0.9a3
Severity: normal | Resolution: invalid
Keywords: |
------------------------------------+---------------------------------------
Changes (by godoy):
* status: new => closed
* resolution: => invalid
Comment:
Answered on the ML:
[TurboGears] Re: Lack of table.q.field mappings for ForeignKey columns in
SQLObject.
From:
Robin Haswell <[EMAIL PROTECTED]>
To:
[email protected]
Date:
Tue Apr 25 19:33:19 2006
Hey
Quickie post because I gotta go to bed. This bit me a few nights ago,
quick answer:
class Foo(SQLObject):
bar = ForeignKey("Baz")
Column is Foo.q.bazID
You can do Foo.select(AND(Foo.q.bazID == Baz.q.id, Baz.q.something ==
"whatever"))
I agree. SO is rubbish in this respect.
Night night.
-Rob
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/787>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" 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-tickets
-~----------~----~----~----~------~----~------~--~---
