Re: [sqlite] Questions about "INTEGER PRIMARY KEY AUTOINCREMENT" and "UPDATE"

On Thu, 21 Nov 2013 07:29:49 -0600 John McKown wrote: > To get more to your question, what I would do is have another, > boolean, column in my table. I would call it something like > "being_edited". When a user wants to edit a car, I would start a > transaction

Re: [sqlite] Does sqlite has db file-size restriction on Solaris 10?

Hi, Simon, I use the 64bit Solaris 10 and the fs type is ufs. The trace as below: bash-3.00# df -v Mount Dir Filesystemblocks used free %used /dev/dsk/c0t5000CCA01286BB88d0s0 / 94601683 4847315

Re: [sqlite] Does sqlite has db file-size restriction on Solaris 10?

On 23 Nov 2013, at 1:03am, Liang Kunming wrote: > I meet some issue when use the sqlite on Solaris 10. The db file is made by > the sqlite R3.4.2 version and the sqlite3 is compiled on Solaris 10 platform > (has attached). When the db file meet 2147483648 bytes

Re: [sqlite] Does sqlite has db file-size restriction on Solaris 10?

Hi, everyone, I meet some issue when use the sqlite on Solaris 10. The db file is made by the sqlite R3.4.2 version and the sqlite3 is compiled on Solaris 10 platform (has attached). When the db file meet 2147483648 bytes (2Gigabytes), the file size can not increase anymore, and query/write

Re: [sqlite] WAL and long-lived prepared statements

Sascha Sertel wrote: > While our long lived prepared statements are reset many times throughout > their lifecycle, there are several of them in use at the same time, and > probably never in a state where all of them are reset. The statements feed > a UI and are constantly refreshed, requeried, and

Re: [sqlite] WAL and long-lived prepared statements

On Fri, Nov 22, 2013 at 10:10 AM, Sascha Sertel wrote: > > We actually hold a cache of prepared statements so we know which ones are > open, maybe as an experiment I could try calling reset on all of them and > see if that gives the checkpointer enough time to do its

Re: [sqlite] WAL and long-lived prepared statements

On Nov 22, 2013 6:08 AM, "Simon Slavin" wrote: > > > On 22 Nov 2013, at 1:24pm, Clemens Ladisch wrote: > > > Simon Slavin wrote: > >> All statements are entirely enclosed in a transaction. > > > > No, automatic transactions start with the first

Re: [sqlite] Using multiple connections from multiple threads - SQLITE_LOCKED

Hi SQLiteuser, is that really your name? - If so, bless your parents :) Seriously though, it is quite legal (and also done mostly) to have several connections to a database. What you can't do is read data WHILE another thread is writing to it in serializable mode as you are using. The table

[sqlite] SQLite version 3.8.2 running 2.5x faster for some queries.

The www.sqlite.org server logs are stored in an SQLite database (of course). We have a script that is run daily on that database with a dozen or so queries that look something like this: .print .print Downloads in the past 24 hours .mode column .width -6 -6 100 .header on SELECT

Re: [sqlite] WAL and long-lived prepared statements

On 22 Nov 2013, at 1:24pm, Clemens Ladisch wrote: > Simon Slavin wrote: >> All statements are entirely enclosed in a transaction. > > No, automatic transactions start with the first sqlite3_step() and end > with either sqlite3_reset() or sqlite3_finalize(). Thanks,

Re: [sqlite] Performance regression 3.7.13 -> 3.8.1

On Thu, Nov 21, 2013 at 1:30 PM, Andreas Kloeckner wrote: > Hi there, > > I'm encountering a fairly severe performance regression ("too quick to > notice" -> "multiple seconds") with SQLite 3.8.1 as compared to > 3.7.13. Both versions are installed from packages shipped by

[sqlite] Using multiple connections from multiple threads - SQLITE_LOCKED

Hi. Is it legal to use multiple connections to a database when the db is in serialized mode and wal is enabled. Additionally i would like to open the connections and use them from several threads. I keep getting SQLITE_LOCKED errors and cannot read from the db when a write transaction from another

[sqlite] Performance regression 3.7.13 -> 3.8.1

Hi there, I'm encountering a fairly severe performance regression ("too quick to notice" -> "multiple seconds") with SQLite 3.8.1 as compared to 3.7.13. Both versions are installed from packages shipped by Debian. I've attached the command line and output for an "explain" of both queries below.

Re: [sqlite] WAL and long-lived prepared statements

Simon Slavin wrote: > All statements are entirely enclosed in a transaction. No, automatic transactions start with the first sqlite3_step() and end with either sqlite3_reset() or sqlite3_finalize(). Regards, Clemens ___ sqlite-users mailing list

Re: [sqlite] WAL and long-lived prepared statements

On 22 Nov 2013, at 7:39am, Sascha Sertel wrote: > We also switched to WAL journaling mode a while ago and noticed that the > WAL file just keeps growing bigger and bigger, and the checkpointer never > seems to be able to write everything back into the main database file

Re: [sqlite] SQLite scalability

Valentin Davydov wrote: On Thu, Nov 21, 2013 at 11:43:32AM +0200, Baruch Burstein wrote: Hi all, I know SQLite is supposed to support DB sizes in the TB (I think the default configuration can reach 1TB). I am curious if anyone actually uses SQlite at anywhere near this. Yes. Does anyone

Re: [sqlite] WAL and long-lived prepared statements

On 11/22/2013 02:47 PM, Dan Kennedy wrote: On 11/22/2013 02:39 PM, Sascha Sertel wrote: Hello everybody, the app I'm working on heavily relies on use and reuse of prepared statements, many of them are reset many times but not finalized until the end of the application lifetime. We also

Re: [sqlite] SQLite scalability

On Thu, Nov 21, 2013 at 11:43:32AM +0200, Baruch Burstein wrote: > Hi all, > > I know SQLite is supposed to support DB sizes in the TB (I think the > default configuration can reach 1TB). I am curious if anyone actually uses > SQlite at anywhere near this. Yes. > Does anyone use it regularly

Re: [sqlite] SQLite scalability

On Thu, 21 Nov 2013 11:43:32 +0200 Baruch Burstein wrote: > Hi all, > > I know SQLite is supposed to support DB sizes in the TB (I think the > default configuration can reach 1TB). I am curious if anyone actually uses > SQlite at anywhere near this. Does anyone use it