Re: [sqlite] sqlite3_get_table() failed with error "database is locked"

On 4 Oct 2018, at 10:57am, ldl wrote: > Just the same application started in multiple processes doing the same > things. The accesses to the db were all readonly. > > > I print the error from sqlite3_get_table(). The error is "database is locked". Set a timeout of 60,000ms and see whether

Re: [sqlite] [EXTERNAL] Re: alter table, other alter category, fails in presence of trigger on 3.25.2

The phrase "integer primary key" is the "wingardium leviosa" of the sqlite world. It must be pronouced correctly, lest you end up with a buffalo on your chest. -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Thierry

Re: [sqlite] sqlite3_get_table() failed with error "database is locked"

Hi Clemens, Just the same application started in multiple processes doing the same things. The accesses to the db were all readonly. I print the error from sqlite3_get_table(). The error is "database is locked". Thanks, Liu At 2018-09-24 18:27:24, "Clemens Ladisch" wrote: >ldl

Re: [sqlite] alter table, other alter category, fails in presence of trigger on 3.25.2

Hello Keith, On Thu, Oct 4, 2018 at 1:16 AM Keith Medcalf wrote: > > Unrelated, but are you sure that you want the albums "id int primary key" > and did not happen to misspell "integer" so that the declaration should be > "id integer primary key". In the former case, id is an integer that just