On Wed, Aug 12, 2009 at 12:55 PM, Miguel Tavares<migtava...@gmail.com> wrote:
> Example:
>
> ######################################################
> import sqlobject
>
> class A (sqlobject.SQLObject):
>    name = sqlobject.StringCol (unique=True)
>
> class B (sqlobject.SQLObject):
>    name = sqlobject.StringCol (unique=True)
>    a = sqlobject.RelatedJoin ('A')
>

There isn't a corresponding RelatedJoin definition in class A - since
RelatedJoin is intended to express a Many-to-Many relationship, and
this class structure is one-to-many (B can point to many A's, but A is
unable to point to any B's), that sqlobject doesn't figure out what
you expect it to do here is not that surprising.

It may be worthwhile trying to improve the checks on RelatedJoin to
warn about this case.

-- 
Neil Muller
drnlmul...@gmail.com

I've got a gmail account. Why haven't I become cool?

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss

Reply via email to