While using sqlite3 with node, I used trace and found that a specific query
did not result in a callback invocation. I have only seen this behavior if
all of the following conditions are met:
- sql query includes 'LIKE ?'
- prepare the query
- bind a parameter
- execute the query
If I change the
For Andrea Peri's benefit, I did google and find where someone mentions the
appropriate flags to statically link the dependency in, thus avoiding this
problem.
http://stackoverflow.com/questions/4702732/the-program-cant-start-because-li
bgcc-s-dw2-1-dll-is-missing
So Andrea may wish to rebuild and
Okeydoke. Well, keep in mind, you are already statically linking sqlite
(sort of), and apparently the libsymmeteric as well. ItÂ’s only the gcc
runtime that is dynamically linked. I believe if you just change the flags
as per the article linked, then that will happen with no further effort on
Simon Slavin-3 wrote
When you lose data are you ever losing part of a transaction ? SQLite is
allowed to lose entire transactions, back to some END/COMMIT statement.
It should not be losing parts of transactions. Or, at least, when you
reopen the database using the SQLite library it should
If you give your id columns unambiguous names to begin with, things will work
out a lot better for you in the long run.
May I suggest the following modification to your tables to remove ambiguity:
CREATE TABLE x(
x_id INTEGER
);
CREATE TABLE y(
y_id INTEGER,
x_id INTEGER REFERENCES
Andy Bradford wrote:
sqlite SELECT strftime('%Y-%m-%d %H:%M:%S',1);
-471-11-25 12:00:00
Is this perhaps undefined behavior because it does say %Y has a range of
--?
Yes. (strftime always outputs the year with four characters, whatever
they might be.)
Regards,
Clemens
On Thu, Sep 25, 2014 at 5:58 PM, Hody Crouch hody.cro...@gmail.com wrote:
While using sqlite3 with node, I used trace and found that a specific query
did not result in a callback invocation. I have only seen this behavior if
all of the following conditions are met:
- sql query includes 'LIKE
Test code is provided below. If you change the sql query to include 'val2
= ?' rather than 'val2 LIKE ?', you will see trace output.
#include stdio.h
#include stdlib.h
#include sqlite3.h
static void trace_callback( void* udp, const char* sql ) {
printf(TRACE: %s\n, sql);
};
int main(int
On Fri, Sep 26, 2014 at 6:44 PM, Hody Crouch hody.cro...@gmail.com wrote:
Test code is provided below. If you change the sql query to include 'val2
= ?' rather than 'val2 LIKE ?', you will see trace output.
It works fine when I try it:
drh@bella:~/sqlite/bld$ gcc -g -I. x1.c sqlite3.o -ldl
