Clifford Heath <no / spam.please.net> wrote:

> 
> The transaction won't help, you get the error from starting
> a transaction while one is already running.
> 
> Put a begin... rescue=>e ... end around your db access code,
> and in the rescue clause, print e.backtrace (it's an array).
> That'll tell you exactly where the error is being thrown.
> 
> Go and read the code of the sqlite adapter, and don't be afraid
> to fill it full of print statements. I personally favour:
> 
> print "message: "+caller*"\n\t"
> 
> If you can't *then* see why your code is violating SQLite's
> non-reentrant requirement, come back and ask again, with code
> samples. In other words, debug it yourself before asking here
> again. Nothing strange or magical is happening. There is an
> error in the code, and we can't find it for you.

OK, i'm trying that.

-- 
Une Bñ×ue