Re: [sqlite] CLI .parameter command observations/request

On 16 Aug 2019, at 4:40pm, Martin wrote: > select * from sqlite_parameters You are expected to create this table yourself, either directly or by using one of the parameter commands. See This sequence works. You should be able to use it to

[sqlite] Bug: LSM1 lsm1BestIndex() always chooses table scan

Hi SQLite devs, I'd like to begin with a "thank you" for a great tool that we use every day at Internet Archive. We are currently considering SQLite's LSM engine (we are aware it is not considered production quality) to implement a index server process that will underpin the Wayback Machine's

[sqlite] CLI .parameter command observations/request

Hi, first a thankyou to everyone who helped with my 'date check clause' post. This time I am grappling with the precompiled CLI .parameter command. (The first line in the param.cli file is .echo on) SQLite version 3.29.0 2019-07-10 17:32:03 sqlite> .read param.cli .tables -- select * from

Re: [sqlite] Schema updates across threads in WAL & multithread mode

To clarify, we add a column on our writer connection, and then "SELECT * FROM table" on the reader connection does not include the column that was added. Ben On Fri, Aug 16, 2019 at 11:32 AM Ben Asher wrote: > Hi folks! We're running (sqlite 3.27.2) into an issue where we make a > schema

Re: [sqlite] Schema updates across threads in WAL & multithread mode

On 8/16/19, Ben Asher wrote: > > Is there something we need to do proactively to ensure that schema update > appears immediately from other threads? > When a database connection has a read transaction open, it continues to see a snapshot of the database as it existed when the read transaction

Re: [sqlite] Schema updates across threads in WAL & multithread mode

On 16 Aug 2019, at 7:32pm, Ben Asher wrote: > we make a > schema update (adding a column to a table) on our writer connection Can I ask the maximum number of columns you expect to exist in that table ? I'm working up to trying to convince you to add a row to something instead, but I want to

Re: [sqlite] Determining column collating functions

Would you consider implementing this not as a pragma, but as a real statement, like MySQL's SHOW COLUMNS (https://dev.mysql.com/doc/refman/5.5/en/show-columns.html)? Would be easier to memorize. - Original Message - From: Keith Medcalf To: SQLite mailing list Sent: Wednesday, August

Re: [sqlite] Backward compatibility vs. new features (was: Re: dates, times and R)

Another reason: because PostgreSQL supports it as well (including timezone) ;-) - Original Message - From: Peter da Silva To: SQLite mailing list Sent: Tuesday, August 13, 2019, 23:18:29 Subject: [sqlite] Backward compatibility vs. new features (was: Re: dates, times and R) If the

Re: [sqlite] Schema updates across threads in WAL & multithread mode

Ben Asher, on Friday, August 16, 2019 02:32 PM, wrote... > > Hi folks! We're running (sqlite 3.27.2) into an issue where we make a > schema update (adding a column to a table) on our writer connection, but > then the schema update isn't immediately available on the read-only > connections that we

Re: [sqlite] Getting a notification when a write lock is released.

test user, on Friday, August 16, 2019 02:29 PM, wrote... > > Thanks for the example José. You're welcome. Just thought I would provide some idea... :-) josé ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

[sqlite] Schema updates across threads in WAL & multithread mode

Hi folks! We're running (sqlite 3.27.2) into an issue where we make a schema update (adding a column to a table) on our writer connection, but then the schema update isn't immediately available on the read-only connections that we use on other threads, which causes a crash in our application (app

Re: [sqlite] Getting a notification when a write lock is released.

Thanks for the example José. I was thinking of a more general method that would work when I do not control all of the clients. Your example would only work when all clients are aware of and use the locking logic. On Fri, Aug 16, 2019 at 3:39 PM Jose Isaias Cabrera wrote: > > test user, on

Re: [sqlite] Getting a notification when a write lock is released.

test user, on Thursday, August 15, 2019 07:35 PM, wrote... > The reason for the notification is to minimize time spent waiting. I will tell you what I did with 10 PMs working with a shared windows drive with an SQLite DB. But, take it with a grain of salt, unless you have high-blood pressure,

Re: [sqlite] [EXTERNAL] Re: Documentation update request

On Fri, Aug 16, 2019 at 3:15 AM Hick Gunter wrote: > Reminds me of "... two mice ran up the clock, the clock struck one, and > the other escaped with minor injuries" > 'Twas my impetus (rather than the wording that mistakenly sounded like I was "besmirching" Dr. Hipp) > > -Ursprüngliche

Re: [sqlite] [EXTERNAL] Re: Getting a notification when a write lock is released.

Maybe you are looking for semaphores. These can be tricky to use correctly in the case of cooperating processes, where you have to handle the case of the current owner of the semaphore terminating within the monitored section of code. -Ursprüngliche Nachricht- Von: sqlite-users

Re: [sqlite] [EXTERNAL] Re: Documentation update request

Reminds me of "... two mice ran up the clock, the clock struck one, and the other escaped with minor injuries" -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Kevin Benson Gesendet: Donnerstag, 15. August 2019 20:40 An: