[Tutor] Re: memory problem (II part)

hcohen2 hcohen2 at comcast.net
Mon Jan 19 15:11:50 EST 2004

Guillermo Fernandez Castellanos wrote:

> On Fri, 16 Jan 2004 06:40:00 -0500, Rick Pasotto <rick at niof.net> wrote:
>> >Could the problem come from the cursor or database variable?
>> Have you tried cursor.close() after you've finished processing the
>> returned data?
> Hi,
> It does not work. The only thing that makes the RAM go down is to 
> close the database. I'll try to live with that (closing and opening 
> the database for each command...), even if it's not very clean, and 
> use the del command with closing databases...
> Thanks for the help.
> Guille
> _______________________________________________
> Tutor maillist  -  Tutor at python.org
> http://mail.python.org/mailman/listinfo/tutor

I am perplexed, what product are you using and how heavily are you 
pounding on it?

Why are you using a cursor, which is a known memory hog?  I was 
forbidden using cursors (as were the others in our group), because it 
impacts performance so extremely under Sybase.  Oracle seems to have 
relied upon cursors much longer than competing products due to its tie 
in with the user interface (and packaged tools).  However, finally they 
too have added temporary tables that are much more efficient and 
automatically cleanup after themselves.


More information about the Tutor mailing list