On Nov 10, 2008, at 9:05 AM, Julien Cigar wrote:
>
> One solution is to use server side cursors, but it only works with
> PostgreSQL at the moment (and you can't use server side cursors with
> the
> ORM).
you can. set server_side_cursors=True on your create_engine() call
when using the pos
Note that a lot of database drivers cache *everything* in memory when
you .fetchall(), fetchone() or fetchmany(x). So all those operations
consume the same amout of memory :
result = cursor.execute(...)
for i in result:
...
data = result.fetchall()
for i in data:
...
data = result.fetcho
Thanks Simon - just checked and I'm running 2.5.2 on my machines.
>From experimenting - I'm not so sure I have a memory leak, so much as
just using a lot of memory.
I didn't realise that when Python frees memory, it doesnt necessarily
become free in Linux. I think that possibly all that's happen
> -Original Message-
> From: sqlalchemy@googlegroups.com
> [mailto:[EMAIL PROTECTED] On Behalf Of joelanman
> Sent: 10 November 2008 00:21
> To: sqlalchemy
> Subject: [sqlalchemy] Re: Memory leak - is session.close() sufficient?
>
>
> Thanks for all the advic
Thanks for all the advice - I've changed my unicode settings and
upgraded Beaker, but still have something to fix.. I'll report back if
I find it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To
On Nov 7, 2008, at 10:17 AM, joelanman wrote:
>
> Thanks for that - I'll check out those options - I am using Beaker for
> cache and sessions.
OK, with Beaker, if you are caching things on a dynamically generated
key, such as a key constructed from arbitrary parameters, I strongly
recommend
Thanks for that - I'll check out those options - I am using Beaker for
cache and sessions.
In the meantime I found this post about a leak in MySQLdb 1.2.2 when
using charset=UTF8, which I am:
http://jjinux.blogspot.com/2008/09/python-debugging-memory-leaks.html
I'm using SQLA to do all databa
On Nov 7, 2008, at 6:21 AM, joelanman wrote:
>
> Hi,
>
> I'm getting a memory leak with my app - the stack is apache2,
> mod_wsgi, web.py - and then a lot of sqlalchemy and my own code. The
> issue may well not be with my usage of SQLA - just making sure there's
> nothing I might be doing wrong
