Re: [sqlite] Issues with sqlite3session_attach(conn, NULL) w/ duplicate table in temp

Dan, I tried the above patch and it resolves the issue! Also you were right about use of "*" in attach. I misinterpreted the output of my test in that case. Thank you so much for taking the time to fix this! When can I expect this patch to make it into a release? Adam Levy On Thu, Fe

[sqlite] Issues with sqlite3session_attach(conn, NULL) w/ duplicate table in temp

Hi all When I have a database connection with a temp table of the same name as a table in main, I am getting what I feel is unexpected behavior from the session extension. Most succinctly, I start a session on a connection on the main db with a table with an INTEGER PRIMARY KEY, attach it to all

[sqlite] Typo in docs

The documentation for PRAGMA schema_version has a small grammar error in the first sentence: "The schema_version pragma will to get or set the value of the schema-version integer at offset 40 in the database header. " Note the "will to get or set". The "to" should be removed. Thanks Adam

Re: [sqlite] Last record

Why can't the knowledge of the "last row" be obtained and used by the application after _step returns SQLITE_DONE? Although what Doug suggested could work, it doesn't make sense to me to add an extra count or max query just to know how many results will be returned when those results will be

[sqlite] Ensure a snapshot remains readable

n). This means that a snapshot cannot be taken on a wal mode database with no wal file immediately after it is first opened. At least one transaction must be written to it first." Thank you Adam Levy ___ sqlite-users mailing list sqlite-users@ma

[sqlite] Ensure WAL file for sqlite3_snapshot_get

One of the requirements for sqlite3_snapshot_get is that "One or more transactions must have been written to the current wal file since it was created on disk (by any connection). This means that a snapshot cannot be taken on a wal mode database with no wal file immediately after it is first