LUES ('foo');
sqlite> .header on
sqlite> SELECT v.a FROM a v;
a
foo
sqlite> SELECT v.a FROM b v;
v.a
foo
--
Lapo Luchini - http://lapo.it/
“Never worry about theory as long as the machinery does what it's
supposed to do.” (Robert A. Heinlein, "Waldo & Magic, Inc.&
configure and Makefile have ways to define SQLITE_THREAD_OVERRIDE_LOCK=1
and SQLITE_ALLOW_XTHREAD_CONNECT=1 but those flags are used nowhere in
the source code.
Couldn't them be removed from configure/Makefile too, for the sake of
avoiding confusion?
--
Lapo Luchini - http://lapo.it/
I noticed that sqlite3 command doesn't dump the user_version PRAGMA,
though that would arguably be necessary for the correct work of the
application (or it wouldn't have set it at all, I guess).
Was it simply forgot or is there a specific reason not to dump that?
--
Lapo Luch
would not be a problem in my case)
More memory used? per query o per row?
Less efficient or somewhat slower?
Or simply it is an unsupported option with no known cons but not tested
enough yet?
cheers,
--
Lapo Luchini - http://lapo.it/
___
sqlite-use
lumn anyway (but the column does have
"affinity", so that an integer put in a TEXT column gets converted to
text).
INT, SMALLINT or ANYTHINGINT will be INTEGER value anyway.
See paragraph "2.1 Determination Of Column Affinity" for more info.
- --
Lapo Luchini
[EMAIL PROTEC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think I found a small glitch or, maybe, consider it a request for
enhancement ;-)
% sqlite3 prova
SQLite version 3.2.5
Enter ".help" for instructions
sqlite> CREATE TABLE a(b);
sqlite> INSERT INTO a VALUES (X'41424300500051
6 matches
Mail list logo