Re: [sqlite] sqlite3WinOpenReadWrite() in os_win.c

I am posting this as a bug. Walter Meerschaert wrote: I am looking at the code in os_win.c for sqlite3WinOpenReadWrite() and have a question. The routine uses the windows API CreateFile() to open the file. First it checks to see if it can open it read/write and then if that fails, it tries read

[sqlite] sqlite3WinOpenReadWrite() in os_win.c

I am looking at the code in os_win.c for sqlite3WinOpenReadWrite() and have a question. The routine uses the windows API CreateFile() to open the file. First it checks to see if it can open it read/write and then if that fails, it tries read-only. Now, when it tries read/write, it uses

Re: [sqlite] help with sqlite command

Dennis Cote wrote: To get every N'th row after deletions you need some way to assign a series of integers to the result rows. The easiest way I can think of is to create a temporary table from your initial query. Then you can use the modulus operator to select every N'th record from that table

Re: [sqlite] Why can i open a textfile?

D. Richard Hipp wrote: Most people who are using SQLite successfully have, I imagine, either written their own wrappers around the core API (which is not hard as I do provide you with a lot of helper routines such as sqlite3_vmprintf and friends) or they are using an existing wrapper written

Re: [sqlite] Why can i open a textfile?

I agree, since that makes error/exception handling easier. On the subject of open(), I also would like it to have a read_only option, if that is possible. I am not even sure that a read-only state is tracked through the library, or if the writing attempts just fail with an file access error.