On Thu, Jul 23, 2009 at 6:29 PM, Stef Mientki wrote:
>
> but because the same SQL-statement in Delphi performed well,
> I thought it was a problem with the Python implementation.
Same SQL, but were you also using Sqlite in Delphi?
--
David
blog: http://www.traceback.org
twitter: http://twitter.c
Stef Mientki schrieb:
> hello,
>
> until now I used only small / simple databases in Python with sqlite3.
> Now I've a large and rather complex database.
>
> The most simple query (with just a result of 100 rows),
> takes about 70 seconds.
> And all that time is consumed in "cursor.fetchall"
>
>
Che M wrote:
On Jul 23, 3:58 pm, Stef Mientki wrote:
Piet van Oostrum wrote:
Stef Mientki (SM) wrote:
SM> btw, I don't know if it's of any importance, the SQL-statement I perform is
SM> select OPNAMEN.*, NAME, NAME_, SCORES.SCORE, PATIENT.*
SM> from OPNAMEN
SM>i
On Jul 23, 3:58 pm, Stef Mientki wrote:
> Piet van Oostrum wrote:
> >> Stef Mientki (SM) wrote:
>
> >> SM> btw, I don't know if it's of any importance, the SQL-statement I
> >> perform is
> >> SM> select OPNAMEN.*, NAME, NAME_, SCORES.SCORE, PATIENT.*
> >> SM> from OPNAMEN
> >> SM> inner
On Thu, Jul 23, 2009 at 4:29 PM, Nick Craig-Wood wrote:
> In all the databases I've used, the like operator has been case
> insensitive, so if that is the problem you could use
This is not true in all databases! Many times, this is something that
is configurable when setting up the database serve
David Stanek wrote:
> On Thu, Jul 23, 2009 at 9:02 AM, Stef Mientki wrote:
> >
> > btw, I don't know if it's of any importance, the SQL-statement I perform is
> > select OPNAMEN.*, NAME, NAME_, SCORES.SCORE, PATIENT.*
> > from OPNAMEN
> > inner join POID_VLID on OPNAMEN.POID
David Stanek wrote:
On Thu, Jul 23, 2009 at 9:02 AM, Stef Mientki wrote:
btw, I don't know if it's of any importance, the SQL-statement I perform is
select OPNAMEN.*, NAME, NAME_, SCORES.SCORE, PATIENT.*
from OPNAMEN
inner join POID_VLID on OPNAMEN.POID= POID_VLID.POID
Piet van Oostrum wrote:
Stef Mientki (SM) wrote:
SM> btw, I don't know if it's of any importance, the SQL-statement I perform is
SM> select OPNAMEN.*, NAME, NAME_, SCORES.SCORE, PATIENT.*
SM> from OPNAMEN
SM>inner join POID_VLID on OPNAMEN.POID= POID_
> Stef Mientki (SM) wrote:
>SM> btw, I don't know if it's of any importance, the SQL-statement I perform is
>SM> select OPNAMEN.*, NAME, NAME_, SCORES.SCORE, PATIENT.*
>SM> from OPNAMEN
>SM>inner join POID_VLID on OPNAMEN.POID=
>POID_VLID.POID
>SM>inner join VRA
On Thu, Jul 23, 2009 at 9:02 AM, Stef Mientki wrote:
>
> btw, I don't know if it's of any importance, the SQL-statement I perform is
> select OPNAMEN.*, NAME, NAME_, SCORES.SCORE, PATIENT.*
> from OPNAMEN
> inner join POID_VLID on OPNAMEN.POID = POID_VLID.POID
> inner join
Tim Chase wrote:
until now I used only small / simple databases in Python with sqlite3.
Now I've a large and rather complex database.
The most simple query (with just a result of 100 rows),
takes about 70 seconds.
And all that time is consumed in "cursor.fetchall"
Using the same database in Del
until now I used only small / simple databases in Python with sqlite3.
Now I've a large and rather complex database.
The most simple query (with just a result of 100 rows),
takes about 70 seconds.
And all that time is consumed in "cursor.fetchall"
Using the same database in Delphi,
using the sam
hello,
until now I used only small / simple databases in Python with sqlite3.
Now I've a large and rather complex database.
The most simple query (with just a result of 100 rows),
takes about 70 seconds.
And all that time is consumed in "cursor.fetchall"
Using the same database in Delphi,
using
13 matches
Mail list logo
