Re: [sqlite] Write-Ahead Logging -- documentation error

After some head scratching, I’ll retract my previous message. The documentation (as revised last week) is correct. The previous version of wal.html mentioning “read mark” had led me down the wrong path in understanding which bit of the WAL was protected while a read lock was active. There is

Re: [sqlite] Postgres vs MySQL (was Re: Messages posted on Nabble not getting to list)

Good summary, agree 100%. >From experience, Postgres is amazingly configurable, if you ever want to do something weird. Sqlite is too, but only if you access it directly in C and don't really need a server. And the guys working on the internals (both) are the smartest bunch you're likely to run

Re: [sqlite] Sweet 16

On 2016-05-29 10:28 AM, Richard Hipp wrote: The first check-in of SQLite code occurred 16 years ago today. https://www.sqlite.org/src/timeline?c=2000-05-29 Congratulations on that! Thank you for all of that work. Stay strong and keep moving on. Coincidentally, that first commit date is

[sqlite] Postgres vs MySQL (was Re: Messages posted on Nabble not getting to list)

On 2016-05-28 12:49 PM, r.a.n...@gmail.com wrote: @Daren Any reasons for the thumbs down on MySQL? Their workbench is better that Toad ... On May 27, 2016, at 10:00 PM, Darren Duncan wrote: On 2016-05-27 2:28 PM, Balaji Ramanathan wrote: But when I was debating

Re: [sqlite] Messages posted on Nabble not getting to list

It was too much database for my purposes as far as this project was concerned. Same with PostgreSQL. Also, I wanted something that would be easily accessible from my android phone/tablet as well as my PC. I have been using MS Access all along, and I really like the nice front end and reporting

Re: [sqlite] constraint failed message and no clue what went wrong

On Monday, May 23, 2016, Bernd Lehmkuhl wrote: > > > Dominique Devienne > hat am 23. Mai > 2016 um 13:42 > Could it be your you "knoten" and "punkte" tables have values with the > same IDs? > > Gotcha! Thanks. Even though I claimed

Re: [sqlite] Sweet 16

On 29 May 2016, at 18:28, Richard Hipp wrote: > The first check-in of SQLite code occurred 16 years ago today. > https://www.sqlite.org/src/timeline?c=2000-05-29 Congratulations! Keep up the great work. Niall O'Reilly ___ sqlite-users mailing

Re: [sqlite] Sweet 16

Incredible. Congratulations to Richard, Dan, Joe and the rest of the team on this incredible achievement. I'm not very active on this list, but I've been a casual sqLite user for years and it just keeps getting better. Keep up the great work! Kind regards, Philip Bennefall On 5/29/2016 7:28

[sqlite] Sweet 16

The first check-in of SQLite code occurred 16 years ago today. https://www.sqlite.org/src/timeline?c=2000-05-29 -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

[sqlite] Preventing certain query keywords from getting stemmed

Hi, While running queries, sometimes there are technical keywords which shouldn't be stemmed by the tokenizer. For example, if I query for "lfs" (which is a file system), the porter stemmer, converts it to "lf", which matches many other unrelated keywords in the corpus (such as ascii lf or some

Re: [sqlite] BUG: FTS5 query containing OR + order by rank

>> I'm getting "database disk image is malformed" errors when running a >> query containing OR and ordering by rank against a FTS5 index: > What happens when you run > PRAGMA integrity_check > on it ? "ok" (this is on a transient in-memory db) $ sqlite3 SQLite version 3.13.0 2016-05-18