Re: [sqlalchemy] another problem with complex join

2010-02-25 Thread Michael Bayer
Manlio Perillo wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Michael Bayer ha scritto: >> >> On Feb 18, 2010, at 11:55 AM, Manlio Perillo wrote: >> >> Michael Bayer ha scritto: > [...] >> so what I had in mind is that, if its given a join as the left side, >> it just does

Re: [sqlalchemy] another problem with complex join

2010-02-23 Thread Manlio Perillo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Bayer ha scritto: > > On Feb 18, 2010, at 11:55 AM, Manlio Perillo wrote: > > Michael Bayer ha scritto: [...] > so what I had in mind is that, if its given a join as the left side, > it just does the "natural" thing, i.e. joins t

Re: [sqlalchemy] another problem with complex join

2010-02-20 Thread Manlio Perillo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ben De Luca ha scritto: > >> Ok, thanks. >> I have never seen this pattern in use. >> If the import is done inside a function, usually there are no problems >> with circular module import. > > Its a performance gain as the second time you hit that fu

Re: [sqlalchemy] another problem with complex join

2010-02-19 Thread Ben De Luca
> Ok, thanks. > I have never seen this pattern in use. > If the import is done inside a function, usually there are no problems > with circular module import. Its a performance gain as the second time you hit that function you don't have to import it again. -- You received this message becaus

Re: [sqlalchemy] another problem with complex join

2010-02-19 Thread Manlio Perillo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Bayer ha scritto: > [...] > Since we are speaking about _match_primaries, I'm curious to know why > the implementation is: > > def _match_primaries(self, primary, secondary): >global sql_util >if not sql_util: >from sqlalchemy.

Re: [sqlalchemy] another problem with complex join

2010-02-19 Thread Michael Bayer
On Feb 18, 2010, at 11:55 AM, Manlio Perillo wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Michael Bayer ha scritto: >> [...] >>> so what I had in mind is that, if its given a join as the left side, >>> it just does the "natural" thing, i.e. joins to the right. >>> If the "natura

Re: [sqlalchemy] another problem with complex join

2010-02-18 Thread Manlio Perillo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Bayer ha scritto: > [...] >> so what I had in mind is that, if its given a join as the left side, >> it just does the "natural" thing, i.e. joins to the right. >> If the "natural" join isn't available, then it does its usual >> search through

Re: [sqlalchemy] another problem with complex join

2010-02-17 Thread Michael Bayer
On Feb 17, 2010, at 10:25 AM, Manlio Perillo wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Michael Bayer ha scritto: >> On Feb 17, 2010, at 9:19 AM, Manlio Perillo wrote: >> >> Hi. >> >> I have found another limitation of SQLAlchemy, when handling joins. >> The code is here: >>

Re: [sqlalchemy] another problem with complex join

2010-02-17 Thread Manlio Perillo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Bayer ha scritto: > On Feb 17, 2010, at 9:19 AM, Manlio Perillo wrote: > > Hi. > > I have found another limitation of SQLAlchemy, when handling joins. > The code is here: > http://paste.pocoo.org/show/179286/ > > I get: > sqlalchemy.exc.Argu

Re: [sqlalchemy] another problem with complex join

2010-02-17 Thread Michael Bayer
On Feb 17, 2010, at 9:19 AM, Manlio Perillo wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi. > > I have found another limitation of SQLAlchemy, when handling joins. > The code is here: > http://paste.pocoo.org/show/179286/ > > I get: > sqlalchemy.exc.ArgumentError: Can't determ

[sqlalchemy] another problem with complex join

2010-02-17 Thread Manlio Perillo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. I have found another limitation of SQLAlchemy, when handling joins. The code is here: http://paste.pocoo.org/show/179286/ I get: sqlalchemy.exc.ArgumentError: Can't determine join between 'Join object on Join object on content_types(159586732) an