Re: [sqlite] Non-keyword quoted identifiers parsed as string literals

2019-08-31 Thread Ben Kurtovic
> Is this working as intended? Are there plans to make SQLite reject such > examples as malformed queries instead of implicitly coercing? This problematic behavior, including discussion on how to disable it, is documented here: https://www.sqlite.org/quirks.html#dblquote

[sqlite] Non-keyword quoted identifiers parsed as string literals

2019-08-31 Thread William Chargin
I tracked down a perplexing issue to the following behavior: sqlite> CREATE TABLE tab (col); sqlite> SELECT nope FROM tab; -- fails; good Error: no such column: nope sqlite> SELECT "nope" FROM tab; -- works? sqlite> INSERT INTO tab (col) VALUES (77); sqlite> SELECT col FR

Re: [sqlite] Endless loop possible with simultaneous SELECT and UPDATE?

2019-08-31 Thread Keith Medcalf
> Having read : https://www.sqlite.org/isolation.html > Specifically the line "And the application can UPDATE the current row > or any prior row, though doing so might cause that row to reappear in a > subsequent sqlite3_step()." > Is it possible to create and endless loop Eventually you will h

[sqlite] Endless loop possible with simultaneous SELECT and UPDATE?

2019-08-31 Thread Alexander Vega
Having read : https://www.sqlite.org/isolation.html Specifically the line "And the application can UPDATE the current row or any prior row, though doing so might cause that row to reappear in a subsequent sqlite3_step()." Is it possible to create and endless loop with the following (pseudo)code?

Re: [sqlite] Unexpected REINDEX behavior.

2019-08-31 Thread dirdi
On 8/30/19 3:59 AM, dirdi wrote: > Do not bother! - "bother!" + "worry!" Sorry @Keith, English is only a second language to me and sometimes I mix-up idioms. You all were very helpful and I learned a lot so far. I just feel a bit dumb right now =/ -- Best regards dirdi

Re: [sqlite] Tracking item history using SQLite

2019-08-31 Thread Rob Willett
Hi, We have a very similar system that captures traffic incident information such as accidents, roadworks, traffic jams and sends personalised information to drivers based on their routes. We realised after a few years that our original design for the database was inefficient as we had a sin