> On 2/7/20, chiahui chen wrote:
>>
>> I tried the suggested solution. sqlite3 was
>> downloaded and compiled.
>> Then ran : gcc -g -l. -fPIC -dynamiclib ./ext/csv.c -o csv.dylib
^^^
Is this a typo? This should read
gcc -I.
>> the same errors occurred again.
While being able to use Tcl variable references inside db eval SQL
statements (as in
set name "foo'bar"
db eval {SELECT * FROM sometable WHERE somecolumn = $name}
) this does work only for "simple" Tcl variable references.
This script shows this:
package require sqlite3
sqlite3 db ":memory:"
The fix http://www.sqlite.org/cgi/src/info/4f1b5229a3bbc9d4 (Escape
control characters in JSON) introduced a regression.
> ./sqlite3
SQLite version 3.19.0 2017-04-12 17:50:12
[...]
sqlite> select json('"ä"');
Error: malformed JSON
I'd expect: "ä"
The reason is
Am 04/09/2017 10:34 AM, Olivier Mascia wrote:
Le 9 avr. 2017 à 03:08, Jens Alfke <j...@mooseyard.com> a écrit :
On Apr 7, 2017, at 5:26 PM, Rolf Ade <r...@pointsman.de> wrote:
./sqlite3
SQLite version 3.19.0 2017-04-07 20:20:08
[...]
sqlite> select json(' { "this" : 00
> ./sqlite3
SQLite version 3.19.0 2017-04-07 20:20:08
[...]
sqlite> select json(' { "this" : 000.23 } ');
{"this":000.23}
If I read RFC 7159 (http://www.rfc-editor.org/rfc/rfc7159.txt) correct
this should return: "Error: malformed JSON".
http://sqlite.org/json1.html say, the json1 support "is
> sqlite3 two tmp.db
> two busy busyhandler
>
> catch {two eval { DELETE FROM some }} errMsg
> puts $errMsg
> two timeout 500
> catch {two eval { DELETE FROM some }} errMsg
> puts $errMsg
> two busy busyhandler
> catch {two eval { DELETE FROM some }} errMsg
>
Rowan Worth <row...@dug.com> writes:
> On 28 October 2016 at 02:53, Rolf Ade <r...@pointsman.de> wrote:
>
>> Another plea, since I'm already writing: It isn't immediate and without
>> any doubt clear, how the "timeout" and the "busy" met
ETE FROM some }} errMsg
puts $errMsg
Rolf Ade <r...@pointsman.de> writes:
> 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 documenta
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.
Hello,
I'm asking this for further discussion of a deficiencies of emacs
sql-mode w/ sqlite databases
(https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23566).
What suffixes to sqlite database files do you use or see in the wild?
There are for sure
.db (e.g. firefox)
.sqlite[23]?
Hello,
I'm asking this for further discussion of a deficiencies of emacs
sql-mode w/ sqlite databases
(https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23566).
If the cmd line tool sqlite3 is used, is it possible to damage a file,
given as sqlite database file argument to sqlite3?
Just
sqlite3
Richard Hipp writes:
> A change summary for 3.13.0 is at
> https://www.sqlite.org/draft/releaselog/3_13_0.html
Change the temporary directory search algorithm on Unix to allow
directories read and execute permission, but without read permission, to
serve as temporary directories.
Am 11/17/2015 11:32 PM, Richard Hipp wrote:
> On 11/17/15, Yuri wrote:
>> This message always leaves the user wondering: "Which constraint?"
>>
>> How hard is it to add this information to the message? Is this a matter
>> of memorizing the ID of the constraint, and then printing its name in
>>
13 matches
Mail list logo