Thread: [SQLObject] xxx = ForeignKey (this is at least a doc bug)
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: <rdm...@bi...> - 2007-03-20 23:21:57
|
I just spent half a day banging my head against a weird error I was getting from my model when trying to access a MultipleJoin. I built a simple test case that worked fine, and by stripping my original model down piece by piece until it looked like the working case I finally found my bug. My ForeignKey attribute needed to be the translated name of the table it was referencing. This was _very_ surprising. I can't find any mention of this restriction in the docs at http://www.sqlobject.org/SQLObject.html. --David |
From: <rdm...@bi...> - 2007-03-21 00:29:25
|
On Tue, 20 Mar 2007 at 19:20, rdm...@bi... wrote: > I just spent half a day banging my head against a weird error I was > getting from my model when trying to access a MultipleJoin. I built a > simple test case that worked fine, and by stripping my original model > down piece by piece until it looked like the working case I finally > found my bug. > > My ForeignKey attribute needed to be the translated name of the table > it was referencing. > > This was _very_ surprising. I can't find any mention of this > restriction in the docs at http://www.sqlobject.org/SQLObject.html. OK, just ignore me. I see that my problem was the MultipleJoin and the fact that I didn't realize I needed to specify the joinColumn. Which still means there's a documentation bug, but I'm not sure what the fix would be :) :) --David |
From: <rdm...@bi...> - 2007-03-21 00:31:33
|
On Tue, 20 Mar 2007 at 20:28, rdm...@bi... wrote: > Which still means there's a documentation bug, but I'm not sure > what the fix would be :) :) Actually, thinking about it, what would have saved me the half day would be if the error message I got had mentioned that it was related to the multiple join 'joinColumn'. Then I would have spotted the problem right away. --David |