[sqlite] ODBC Driver

I do not seem to be able to parse a multiple insert statement through the odbc drive using SQLExecDirect(...) I have tried with BEGIN, COMMIT TRANSACTION does anyone have any ideas? Regrards ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] RESOLVED: unable to open database file/Disc I/O error

On Fri, Nov 5, 2010 at 3:25 AM, Serena Lien wrote: > > I would like to inform the group that I managed to resolve the issue with a > workaround. I am not sure if this is a bug in vista or whether there might > in fact be some slight issue with sqlite... > > The problem seems

Re: [sqlite] Bugreport: sqlite dot commands should return a vaild returncode

Andreas, The issue here has less to do with dot commands, and more with the database initialization behavior. When you call # /usr/local/bin/sqlite3 ./monitor.dbx .dump > monitor.dump it's going to build the monitor.dbx database file first, then do the dump on the (empty) database. This is

[sqlite] RESOLVED: unable to open database file/Disc I/O error

I would like to inform the group that I managed to resolve the issue with a workaround. I am not sure if this is a bug in vista or whether there might in fact be some slight issue with sqlite... The problem seems to be hardware and software related, and occurs for me when my application is

[sqlite] Bugreport: sqlite dot commands should return a vaild returncode

Hi all, The dot commands of sqlite CLI (.dump, .import, ...) should implement a correct exception handling. For example: If a database file doesn't exist or the database is locked by another sqlite process, then sqlite returns exit code 0 and no error message. I would expect a non-zero exit