Re: [SQLObject] MultipleJoin inactive in version 0.6

[Carlos R. <car...@gm...>]

On Tue, 02 Nov 2004 13:25:12 +0200, Max Ischenko <ma...@uc...> wrote:
> IMO, either the docs must be updated or, better yet, SQLobject should
> somehow figure out that joinedColumn argument by itself.

Judging by the mailing list messages, that's at least the fourth time
someone (including myself) have fallen on this trap recently. I've
proposed a change to the documentation about two weeks ago. I don't if
Ian noticed it, though. What I found is that this is something hard to
explain in a clean and short way, exactly because SQLObject does such
a great job to hide the complexity behind the relationship mechanism.
We just expect it to be able to detect automatically the column name,
which it can't do for the generic case. The reason only becomes clear
when we think in terms of the underlying schema.

-- 
Carlos Ribeiro
Consultoria em Projetos
blog: http://rascunhosrotos.blogspot.com
blog: http://pythonnotes.blogspot.com
mail: car...@gm...
mail: car...@ya...