[sqlite] ODBC driver for C error "only one SQL statement allowed"
Hi, sqlite-users, am evaluating Sqlite ODBC driver for C (current sqliteodbc.exe by Ch. Werner, http://www.ch-werner.de/sqliteodbc/). After defining successfully two tables "mytable" and "mysequence", I tried to define a trigger by means of "CREATE TRIGGER trg BEFORE INSERT ON mytable FOR EACH ROW BEGIN INSERT INTO mysequence VALUES(0); END" This worked fine with sqlite3.c, when passed to sqlite3_exec(), but gave rise to an error message with sqlite3odbc.c , when passed to SQLExecDirect(). The message was : "only one SQL statement allowed". Is there a special SQL syntax required for sqlite3odbc? Are there any (further) restrictions for triggers? Or is it a bug? Best regards Martin Abshagen ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Recall: ODBC driver C source file includes a header which was not shipped
Hi, I realize I have to recall my question. It was my fascination about the "amalgamation" version of sqlite3 that made me think that even sqlite3odbc.c was an "amalgamation". I apologize, should have read README before complaining. Martin Abshagen ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] ODBC driver C source file includes a header which was not shipped
Hi, am trying to use the Sqlite3 ODBC driver for C, provided by Christian Werner (http://www.ch-werner.de/sqliteodbc/, product sqliteodbc-0.77-1.src.rpm). If _WIN32 is defined, sqlite3odbc.c includes a "resource3.h" header file, which is not shipped with the version. How could I work around or find "resource3.h"? Best regards Martin Abshagen ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Does or will Sqlite provide a DUMP mechanism?
Hello all, I am new to Sqlite and I would like to backup Sqlite databases at runtime. Appearently Sqlite does not (yet?) provide a functionality such as mysqlhotcopy. My questions are: Can a backup mechanism be implemented by means of the current Sqlite-API? And if not so: Does anybody plan to add a dump functionality within the next one or two years? Best regards, Martin Abshagen ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
