Re: [pysqlite] problems grokking SQL

Gerhard H=E4ring wrote:
> Eric S. Johansson wrote:
>> this probably belongs on the SQLite list proper but, I can only handle s=
o many
>> negative responses a day.  :-) [...]
> =

> I would have liked to answer, but your post was a bit too vague.

the vagueness is an indication of my problem with understanding. My grockin=
g is
really soft.
> =

> For more specific questions, I'll do my best to give specific answers.

read/modify/write cycle.  how do I do this and guarantee the data will make=
 it
to the database without locking out others.

read a record, do a calculation in python and then write the record as abov=
e.

if record field named state is X, change it to Y

delete all records older than D.  (yes,I have an sqlite datestamp record)

modify/insert.  modify if record exists, insert if it doesn't.  handle race
condition of multiple processes updating.

------
we really should build an faq or idioms list for this kind of thing.