(Sorry, little mistake on the To: field and this didn't go to the list. My
apologies for the one who received this :P)
Hi everybody again, sorry for the delay in answering.
I've been doing some more testing, with both ORMs (SQLO and SQLA) in debug
mode, and seeing the SQL that gets sent to the
On Thu, Apr 01, 2010 at 05:47:06AM -0300, Juan Manuel Santos wrote:
http://pastebin.com/raw.php?i=Xp1TjmZ0
Basically, if you look in the previous link for Setting icon or Setting
thumb you will see that both the icon and the thumb are being set TWICE!
with
the same data.
There are
Yes, you're right and that's a bit odd. I've set the debug variable in the
usual way:
self._conn = connectionForURI(con_str)
self._conn.debug = True
And I noticed this also:
1/Query : CREATE TABLE meta_dir (
[...]
1/QueryR : CREATE TABLE meta_dir (
[...]
Any
On Thu, Apr 01, 2010 at 06:18:35AM -0300, Juan Manuel Santos wrote:
1/Query : CREATE TABLE meta_dir (
[...]
1/QueryR : CREATE TABLE meta_dir (
[...]
Any idea why debug gets printed twice, but the second time with a capital 'r'
after Query? :P
Two debugging output are from
Got it, thanks
One last thing and maybe a bit offtopic: how do I set PRAGMA asyncrhonous =
OFF for the SQLite connection? I'm trying to see if the speed difference is
due to this (as I suspect that SQLA uses PRAGMA), but this:
self._conn.queryAll(PRAGMA synchronous=OFF;)
or this:
One last thing and maybe a bit offtopic:
Offtopic for that thread, so I started a new thread on this new topic.
how do I set PRAGMA asyncrhonous =
OFF for the SQLite connection? I'm trying to see if the speed difference is
due to this (as I suspect that SQLA uses PRAGMA), but this:
I believe I fixed the speed issue. I wrapped the most expensive
functions/calls to SQLObject (expensive in terms of I/O) in a transaction. I
didn't realize that that's the way SQLAlchemy works, and maybe that's why it
was being faster (I had some functions which modified several attributes one
Some examples of the code, so we all can learn from your experiences, will
be nice.
Regards
Petr
On 1 April 2010 21:30, Juan Manuel Santos vicariou...@gmail.com wrote:
I believe I fixed the speed issue. I wrapped the most expensive
functions/calls to SQLObject (expensive in terms of I/O) in
(grr it happened again ., my apologies to the guy who received this mail, it
was intended for the list)
From: Petr Jakeš petr.ja...@tpc.cz
To: vicariou...@gmail.com
Date: Thursday 01 April 2010
Some examples of the code, so we all can learn from your experiences, will
be nice.
Regards
