[clug] mysql programming in python

[jm]

Doesn't really matter about the read only. The forward-only hurts. For 
the moment I've decided that it's just easier to load everything into 
memory as I don't have many records to deal with. The most it is ever 
expected to have to deal with is about 5000 records so loading 
everything into memory is easily do able on modern machines. It 
shouldn'y really matter unless someone else also runs the program and 
starts to play with entries. Luckily, not likely.

thanks,
Jeff.

On 30/11/11 3:53 PM, Arjen Lentz wrote:
> If you're using the MySQL server side cursors: they're read-only and 
> forward-only. If you're using a cursor mechanism implemented in the 
> client code (Python), then it's responsible for keeping track of 
> everything - it can read and not keep previous, or read and remember 
> so you can step backward, or load everything in one hit and just eat 
> memory but allow anything. Cheers, Arjen.