Looking closer it doesn't look like there is a workable SA fix. :-|On 7/25/06, Michael Bayer <[EMAIL PROTECTED]
> wrote:whats the SA fix for this ? other than just documenting, say "join(foo, bar).join(bat)" instead of "join(foo, join(bar, bat))" ?
On Jul 24, 2006, at 10:29 PM, Jonathan Ellis wrot
whats the SA fix for this ? other than just documenting, say "join(foo, bar).join(bat)" instead of "join(foo, join(bar, bat))" ?On Jul 24, 2006, at 10:29 PM, Jonathan Ellis wrote:Looks like sqlite is allergic to the sql generated; works fine in postgres[for test/orm/mapper.py again] def testjoi
On 7/24/06, Jamie Wilkinson <[EMAIL PROTECTED]> wrote:
This one time, at band camp, Jonathan Ellis wrote:>Looks like sqlite is allergic to the sql generated; works fine in postgres>>[for test/orm/mapper.py again]> def testjoin3tables(self):> class Joined(object):
> pass> j =
This one time, at band camp, Jonathan Ellis wrote:
>Looks like sqlite is allergic to the sql generated; works fine in postgres
>
>[for test/orm/mapper.py again]
> def testjoin3tables(self):
> class Joined(object):
> pass
> j = join(users, join(orders, orderitems), isouter=Tr
Looks like sqlite is allergic to the sql generated; works fine in postgres[for test/orm/mapper.py again] def testjoin3tables(self): class Joined(object): pass j = join(users, join(orders, orderitems), isouter=True)
m = mapper(Joined, j, allow_null_pks=True)
5 matches
Mail list logo