Le mercredi 4 avril 2012 17:55:47 UTC+2, Michael Bayer a écrit :
>
> On Apr 4, 2012, at 11:40 AM, Borax wrote:
>
> Le mercredi 4 avril 2012 16:27:39 UTC+2, Michael Bayer a écrit :
>>
>> this all comes down to the nature of the SQL being emitted.
>>
>> what is the SQL being emitted by SQLAlchemy in
On Apr 4, 2012, at 11:40 AM, Borax wrote:
> Le mercredi 4 avril 2012 16:27:39 UTC+2, Michael Bayer a écrit :
> this all comes down to the nature of the SQL being emitted.
>
> what is the SQL being emitted by SQLAlchemy in this case, and what is the SQL
> that should be emitted ? Working with SQ
Le mercredi 4 avril 2012 16:27:39 UTC+2, Michael Bayer a écrit :
>
> this all comes down to the nature of the SQL being emitted.
>
> what is the SQL being emitted by SQLAlchemy in this case, and what is the
> SQL that should be emitted ? Working with SQLAlchemy in a non-trivial way
> implies you
On Apr 4, 2012, at 10:21 AM, Borax wrote:
> Hi,
>
> I'm using SQLAlchemy 0.7.5 in a web application accessing several tables
> containing between 2.5 and 3.5 millions records; these tables are indexed
> correctly.
> Database is Oracle 10g (release 10.2.0.4).
>
> My problem is quite simple : w
Hi,
I'm using SQLAlchemy 0.7.5 in a web application accessing several tables
containing between 2.5 and 3.5 millions records; these tables are indexed
correctly.
Database is Oracle 10g (release 10.2.0.4).
My problem is quite simple : when querying the database through SQLAlchemy
(via "session.