On 28 July 2018 at 05:41, Rune Torgersen wrote:
> > Rowan Worth Thu, 26 Jul 2018 22:02:50 -0700
> >
> > On 26 July 2018 at 05:56, Rune Torgersen wrote:
> >
> > > The databases have been opened with two connections (one for reads, one
> > > for writes), and use the following options:
> > > sq
> Rowan Worth Thu, 26 Jul 2018 22:02:50 -0700
>
> On 26 July 2018 at 05:56, Rune Torgersen wrote:
>
> > The databases have been opened with two connections (one for reads, one
> > for writes), and use the following options:
> > sqlite3_busy_timeout(mDbConn, 500);
> > sqlite3_exec(mDbConn,
On 2018/07/27 12:51 PM, Richard Hipp wrote:
Seem right. If a change happens to the database in the middle of a
backup, the backup automatically restarts, so that at the end of a
backup you are guaranteed to have a consistent copy from a single
point in time (something that you are not guarantee
On 7/25/18, Rune Torgersen wrote:
> Management wants to know if we're doing it correctly, or if there are
> faster/easier ways to do backup (and check).
> Also wants to know if a backup done using the live backup API gives us an
> exact copy (with any possible corruption) or if the backup is rege
On Fri, 27/7/18, Simon Slavin wrote:
Subject: Re: [sqlite] Backup and integrity check questions
To: "SQLite mailing list"
Date: Friday, 27 July, 2018, 6:35
On 27 Jul 2018, at 6:02am, Rowan
Worth
wrote:
> (any writes
On 27 Jul 2018, at 6:02am, Rowan Worth wrote:
> (any writes to a DB are automatically propagated to in-progress backups
> within the same process).
I didn't know that. Thanks. It's clever.
Simon.
___
sqlite-users mailing list
sqlite-users@mailinglis
On 26 July 2018 at 05:56, Rune Torgersen wrote:
> The databases have been opened with two connections (one for reads, one
> for writes), and use the following options:
> sqlite3_busy_timeout(mDbConn, 500);
> sqlite3_exec(mDbConn, "PRAGMA locking_mode = EXCLUSIVE;", 0, 0, 0);
>
Surely thi
On 25 Jul 2018, at 10:56pm, Rune Torgersen wrote:
> Management wants to know if we're doing it correctly, or if there are
> faster/easier ways to do backup (and check).
Please excuse me mentioning things I'm sure you are already doing correctly.
Your question is useful to many users and this
We have an application that has multiple sqlite3 databases (30-40) open with
exclusive locking.
Every night we do a database backup and a database integrity check.
The backup is done using sqlite3_backup_*. The check is done using a "PRAGMA
integrity_check;"
Currently we allow reads/writes whil
9 matches
Mail list logo