QLdb' library installation, now I'm trying to
fix that.
On Friday, September 5, 2014 7:58:43 AM UTC+2, Massimo Di Pierro wrote:
>
> Very strange. What do you think is causing this?
>
> On Wednesday, 3 September 2014 09:44:17 UTC-5, Mehmet A. wrote:
>>
>> *db.ex
*db.executesql()* takes 30 seconds to return a result, despite the fact
that same query takes 0.5-1 second if I try it on the MySQL console or with
the same code on the web2py debug console or on the web2py shell.
I tried the following cases:
... #Irrelevant part of the code
raw_data = dbs.e
ery?
>>
>> See what happens if you get rid of them.
>>
>> On Monday, August 25, 2014 4:54:53 AM UTC-4, Mehmet A. wrote:
>>>
>>> Hi,
>>> db.executesql() takes 30 seconds to return a result while page-loading,
>>> despite the fact th
;= '2014-8-22'
>
> so the timing for that is: 32.046038147
>
> as far as what are the differences, well, web2py does open a transaction
> and then close the transaction...
>
> On Monday, August 25, 2014 9:24:41 AM UTC-7, Cliff Kachinske wrote:
>>
>> Why is
Hi,
db.executesql() takes 30 seconds to return a result while page-loading,
despite the fact that same query takes 0.5-1 second if I try it on MySQL
console or web2py debug console or web2py shell.
[4] dbs._timings
> [('SELECT 1;', 0.01632424926758),
> ('SET FOREIGN_KEY_CHECKS=1;', 0.003999
5 matches
Mail list logo