For anyone interested - yes, that did solve my problem too.
Thanks, dragonfire13!
On 10/18/2011 4:28 PM, Petrucio wrote:
Yes, I've seen your post earlier but haven't had time to test it,
indeed it looks like they are the same problem.
I'll test it later tonight, and let you kn
Yes, I've seen your post earlier but haven't had time to test it,
indeed it looks like they are the same problem.
I'll test it later tonight, and let you know if it solves my problem
too.
Thanks everyone for the inputs.
On Oct 18, 1:01 pm, Dragonfyre13 wrote:
> Could your issue be related to
Since I was already doing calls to gc.collect by hand after releasing
all references, this is unlikely to have a difference over that. One
way I was thinking of [over]-doing it was to do some processing, save
the state, exit the process entirelly, resume where it left of, rince
and repeat.
Obvious
; rows = db(db.mytable.id>0).select(db.mytable.ALL)
> .
> . (do stuff)
> .
> rows = None # remove reference to query result
>
> .
> . (do stuff)
> .
>
> mic
>
> 2011/10/18 Petrucio :
>
>
>
>
>
>
>
> > I'm using dal.py to do some basic
ped early at pylab and have no idea how little/much
work that would be.
Sorry about the noob question, and sorry if it's repeated - I've done
my best to search around and came empty handed.
Thanks,
Petrucio
5 matches
Mail list logo
