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
-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
-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
> 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
-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.
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
-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
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:
>>
-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
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
-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
11 matches
Mail list logo