I certainly apologzize, to rise this a third time; I will stop to do it
again.
Still, I think the documentation of the busy method of the Tcl interface
to sqlite
http://sqlite.org/tclsqlite.html#busy
lacks the information, that the callback procedure will be called with
one argument.
Rolf Ade
Rowan Worth writes:
> On 28 October 2016 at 02:53, Rolf Ade wrote:
>
>> Another plea, since I'm already writing: It isn't immediate and without
>> any doubt clear, how the "timeout" and the "busy" methods play together,
>> if both are used. I suspect, the timeout, if given, determines, how long
I apologzize to rise this again, it may have fallen under the radar for
some reason. It is minor, too.
The documentation of the busy method of the Tcl interface to sqlite
http://sqlite.org/tclsqlite.html#busy
doesn't tell, that the callback procedure is called with one arg, the
"number of times
On 28 October 2016 at 02:53, Rolf Ade wrote:
> Another plea, since I'm already writing: It isn't immediate and without
> any doubt clear, how the "timeout" and the "busy" methods play together,
> if both are used. I suspect, the timeout, if given, determines, how long
> it lasts until the busy ca
The documentation of the busy method at
http://sqlite.org/tclsqlite.html#busy
should be more specific, with regards of the arguments of the Tcl
callback procedure.
The documentation currently reads:
The "busy" method, like "timeout", only comes into play when the
database is locked. Bu
5 matches
Mail list logo