On 27 April 2016 at 13:01, Mark Foley wrote:
>
> Can sqlite handle contention among multiple accessors with read/write if
> the
> accessors are not on the same host? I.e. is locking intrinsic in sqlite
> and any
> accessor from any host is able to determine and set a row/table lock?
>
That depend
On 27 Apr 2016, at 6:01am, Mark Foley wrote:
> I don't know that answer. Would the journal file be an actual file in the
> same
> folder as the database file?
Yes. Given that your database file is called 'local.sqlite', look for other
files in the same folder with names starting with 'local
ue, 26 Apr 2016 22:31:11 -0600
> From: Scott Robison
> To: SQLite mailing list
> Subject: Re: [sqlite] sqlite3 command line, read-only
>
> On Apr 26, 2016 8:16 PM, "Mark Foley" wrote:
> >
> > I'm back with more read-only issues.
> >
> >
On Tue, Apr 26, 2016 at 10:56 PM, J Decker wrote:
> https://www.sqlite.org/wal.html
>
> "5. It is not possible to open read-only WAL databases. The opening
> process must have write privileges for "-shm" wal-index shared memory
> file associated with the database, if that file exists, or else writ
https://www.sqlite.org/wal.html
"5. It is not possible to open read-only WAL databases. The opening
process must have write privileges for "-shm" wal-index shared memory
file associated with the database, if that file exists, or else write
access on the directory containing the database file if th
On Apr 26, 2016 8:16 PM, "Mark Foley" wrote:
>
> I'm back with more read-only issues.
>
> Thanks to postings on this list, I've made progress, but still more
issues.
>
> Using the sqlite3 command-line, I'm attempted to open,
> read-only, a database located on a Windows 7 workstations, from a Linux
I'm back with more read-only issues.
Thanks to postings on this list, I've made progress, but still more issues.
Using the sqlite3 command-line, I'm attempted to open,
read-only, a database located on a Windows 7 workstations, from a Linux server.
I am mounting the Windows volume r/o:
mount //$
On Mon, Apr 25, 2016 at 6:12 PM, Mark Foley wrote:
> Nope: still error:
>
> sqlite3 \
> '*file:*/mnt/tmp/Users/hcarr.HPRS.000/AppData/Roaming/Thunderbird/Profiles/8sbpxrwj.default/calendar-data/local.sqlite?mode=ro'
> \
> "select distinct value from cal_properties where key = 'CATEGORIES'"
> Erro
On 25 Apr 2016, at 5:12pm, Mark Foley wrote:
> Error: unable to open database
> "*file:*/mnt/tmp/Users/hcarr.HPRS.000/AppData/Roaming/Thunderbird/Profiles/8sbpxrwj.default/calendar-data/local.sqlite?mode=ro":
> unable to open database file
That path looks like it has two components which change
On Mon, Apr 25, 2016 at 4:28 PM, Mark Foley wrote:
> I'm running this on Linux. That Windows notation doesn't work.
>
> sqlite3
> "*file:*/mnt/tmp/Users/.../AppData/Roaming/Thunderbird/Profiles/8sbpxrwj.default/calendar-data/local.sqlite\?mode=ro"
> "select distinct value from cal_properties wher
On Mon, Apr 25, 2016 at 3:35 PM, Mark Foley wrote:
> On Mon, 25 Apr 2016 15:14:56 Dominique Devienne
> wrote:
> > Please (re)read the example I included. --DD
> > C:\Users\DDevienne>sqlite3 *file:*new.db?mode=ro
>
> Sorry, perhaps I'm a bit obtuse. I don't see how your example differs from
> min
On Mon, Apr 25, 2016 at 2:53 PM, Mark Foley wrote:
> On Mon, 25 Apr 2016 14:41:30 Dominique Devienne
> wrote:
>
> > Perhaps you're missing the leading file: ? I believe it is required. --DD
>
> No, unless I'm putting it in the wrong place. As I wrote I did:
$ sqlite3 "myDbpath?mode=ro"
>
Pleas
On Mon, Apr 25, 2016 at 2:33 PM, Mark Foley wrote:
> I'm new to the list, so apologies if this has been posted before.
>
> I am using sqlite3 3.7.17 on Linux Slackware64 14.1. I use the sqlite3
> command
> every 10 minutes to query several Thunderbird calendar databases.
> Occasionally, I
> have
On 25 Apr 2016, at 2:28pm, Mark Foley wrote:
> As I just wrote to Richard Hipp, I must not have the .once command, but see
> my reply for a possible solution using .timeout and tell me what you think.
Yep. That should work. In fact it's a better solution than mine.
Simon.
On 25 Apr 2016, at 2:00pm, Mark Foley wrote:
> problem is that the PRAGMA
> statement echo the timeout value to stdout:
>
> sqlite3 "mydbpath" \
> "PRAGMA busy_timeout=5000;select distinct value from cal_properties where key
> = 'CATEGORIES'"
> 5000
> Orange Category
> Green Category
> Blue Ca
On 25 Apr 2016, at 1:33pm, Mark Foley wrote:
> I am using sqlite3 3.7.17 on Linux Slackware64 14.1. I use the sqlite3
> command every 10 minutes to query several Thunderbird calendar databases.
> Occasionally, I
> have a message, "Error: database is locked"; understandable since Thunderbird
>
Mon, 25 Apr 2016 18:21:33 +0200
From: Dominique Devienne
To: SQLite mailing list
Subject: Re: [sqlite] sqlite3 command line, read-only
On Mon, Apr 25, 2016 at 6:12 PM, Mark Foley wrote:
> Nope: still error:
>
> sqlite3 \
> '*file:*/mnt/tmp/Users/hcarr.HPRS.000/AppData/Roaming/Th
nting workstation drives with the intention of changing files.
--Mark
-Original Message-
> From: Simon Slavin
> Date: Mon, 25 Apr 2016 17:15:20 +0100
> To: SQLite mailing list
> Subject: Re: [sqlite] sqlite3 command line, read-only
>
> On 25 Apr 2016, at 5:12pm, Mark Foley
ite mailing list
> Subject: Re: [sqlite] sqlite3 command line, read-only
>
> On Mon, Apr 25, 2016 at 4:28 PM, Mark Foley wrote:
>
> > I'm running this on Linux. That Windows notation doesn't work.
> >
> > sqlite3
> > "*file:*/mnt/tmp/Users/.../Ap
nne
To: SQLite mailing list
Subject: Re: [sqlite] sqlite3 command line, read-only
On Mon, Apr 25, 2016 at 3:35 PM, Mark Foley wrote:
> On Mon, 25 Apr 2016 15:14:56 Dominique Devienne
> wrote:
> > Please (re)read the example I included. --DD
> > C:\Users\DDevienne>sqlite3 *fi
OK, I'll go with that and see if I get any more lock errors.
--Mark
-Original Message-
From: Simon Slavin
Date: Mon, 25 Apr 2016 14:30:26 +0100
To: SQLite mailing list
On 25 Apr 2016, at 2:28pm, Mark Foley wrote:
> As I just wrote to Richard Hipp, I must not have the .once command, b
OK, I'm at 3.7.17, so too old for .once.
--Mark
-Original Message-
> Date: Mon, 25 Apr 2016 09:32:48 -0400
> From: Richard Hipp
> To: SQLite mailing list
> Subject: Re: [sqlite] sqlite3 command line, read-only
>
> On 4/25/16, Mark Foley wrote:
> >
>
Are you referring to the "*file:*" syntax?
--Mark
-Original Message-
> Date: Mon, 25 Apr 2016 15:14:56 +0200
> From: Dominique Devienne
> To: SQLite mailing list
> Subject: Re: [sqlite] sqlite3 command line, read-only
>
> On Mon, Apr 25, 2016 at 2:53 PM, Mar
On 4/25/16, Mark Foley wrote:
> This is probably taking us down another path, but how would my query succeed
> at
> all if I need a lock to read and the DB file itself is read-only?
>
Most systems allow you to obtain a read-lock on a read-only file.
--
D. Richard Hipp
drh at sqlite.org
On 4/25/16, Mark Foley wrote:
>
> Perhaps too old a version of sqlite3? Doing .help does not list .once,
>
Added to SQLite 3.8.5, circa 2014-06-04.
--
D. Richard Hipp
drh at sqlite.org
400
> From: Richard Hipp
> To: SQLite mailing list
> Subject: Re: [sqlite] sqlite3 command line, read-only
>
> On 4/25/16, Mark Foley wrote:
> >
> > I wonder, then, why I get a lock error if the database is read-only in the
> > first
> > place?
>
&g
n Slavin
> Date: Mon, 25 Apr 2016 14:12:27 +0100
> To: SQLite mailing list
> Subject: Re: [sqlite] sqlite3 command line, read-only
>
> On 25 Apr 2016, at 2:00pm, Mark Foley wrote:
>
> > problem is that the PRAGMA
> > statement echo the timeout value to stdout:
>
#x27;"
Orange Category
Green Category
Blue Category
Purple Category
Blue Category,Holidays
Personal
Didn't give an error and didn't echo the 5000 to stdout. Do you suppose that
will work?
--Mark
-Original Message-
> Date: Mon, 25 Apr 2016 09:10:58 -0400
> Fro
On 4/25/16, Mark Foley wrote:
>
> I wonder, then, why I get a lock error if the database is read-only in the
> first
> place?
The reader has to get a read lock in order to prevent a concurrent
writer from changing content out from under it. (Moving the database
to WAL mode allows readers and wri
On 4/25/16, Mark Foley wrote:
>
> Thanks, I just tried that. It's a good ides, but the problem is that the
> PRAGMA
> statement echo the timeout value to stdout:
>
Can you use the ".once /dev/null" command prior to the "PRAGMA" to
suppress the output?
sqlite3 "mydbpath" -cmd ".once /dev/null" -
t for outputting the timeout
value to stdout).
I wonder, then, why I get a lock error if the database is read-only in the first
place?
THX --Mark
-Original Message-
> Date: Mon, 25 Apr 2016 08:42:26 -0400
> From: Richard Hipp
> To: SQLite mailing list
> Subject: Re: [sqlite]
jor editing to my queries to reject the 1st row make the
query processing very depending on whether or no I use the PRAGMA. Is there a
way to surpress the PRAGMA output?
THX --Mark
-Original Message-
> Date: Mon, 25 Apr 2016 13:41:36 +0100
> To: SQLite mailing list
> Subject: Re
27;\?', no go.
Should this work from the command line? Should the '?' go somewhere else? Can
you give a working commandline example?
THX --Mark
-Original Message-
> Date: Mon, 25 Apr 2016 14:41:30 +0200
> From: Dominique Devienne
> To: SQLite mailing list
>
On 4/25/16, Mark Foley wrote:
> I'm new to the list, so apologies if this has been posted before.
>
> I am using sqlite3 3.7.17 on Linux Slackware64 14.1. I use the sqlite3
> command
> every 10 minutes to query several Thunderbird calendar databases.
> Occasionally, I
> have a message, "Error: dat
I'm new to the list, so apologies if this has been posted before.
I am using sqlite3 3.7.17 on Linux Slackware64 14.1. I use the sqlite3 command
every 10 minutes to query several Thunderbird calendar databases. Occasionally,
I
have a message, "Error: database is locked"; understandable since Thun
35 matches
Mail list logo
