ginal Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 09 March 2007 16:36
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] journal - "Unable to open the database file"
>
>
> "Allan, Mark" <[EMAIL PROTECTED]> wrote:
> > 3)
On 3/10/07, Nuno Lucas <[EMAIL PROTECTED]> wrote:
On 3/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Joe Wilson <[EMAIL PROTECTED]> wrote:
> > --- [EMAIL PROTECTED] wrote:
> > > Is there something that the SQLite core can do better?
> >
> > Perhaps exclusive locks on journal files would h
Dave Dyer <[EMAIL PROTECTED]> wrote:
> >
> >The main purpose of the journal is so that if the program
> >or OS crashes or there is a power failure, once the machine
> >reboots and some other process tries to read the database,
> >the other process can see the journal and roll it back.
> >Private an
On 3/10/07, Nuno Lucas <[EMAIL PROTECTED]> wrote:
On 3/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> They are, at least on unix. On unix, both files are opened with
> the O_EXCL flag. How do I do the same thing for windows?
The code does that already. You just pass 0 on the share param
On 3/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Joe Wilson <[EMAIL PROTECTED]> wrote:
> --- [EMAIL PROTECTED] wrote:
> > Is there something that the SQLite core can do better?
>
> Perhaps exclusive locks on journal files would help avoid this problem.
> Or are the -journal and etilqs_* f
This is a code snippet for such a function with Windows and Unix. Even
here the dreaded NFS raises its ugly head. The Windows code has worked
fine, but Windows gurus might find some way to improve it.
/*Open the file if possible in the appropriate mode.*/
#if IS_WIN32
mode = GENERIC_READ;
After I hit it struck me like a bombshell that the journal has to
be there for the next startup to perform its complete function so such a
method would fail. A virtual memory based object would only provide
transactional support, not crash recovery. Humble pie for breakfast!
OS designers c
--- Joe Wilson <[EMAIL PROTECTED]> wrote:
> There's also this - CreateFileTransacted():
>
> http://msdn2.microsoft.com/en-us/library/aa363859.aspx
>
> which has the argument:
>
> dwShareMode
> ...
> If this parameter is 0 (zero) and CreateFileTransacted succeeds,
> the object cann
On 3/10/07, Joe Wilson <[EMAIL PROTECTED]> wrote:
There's also this - CreateFileTransacted():
http://msdn2.microsoft.com/en-us/library/aa363859.aspx
Doesn't this require Vista?
-scott
-
To unsubscribe, send email to
--- [EMAIL PROTECTED] wrote:
> Joe Wilson <[EMAIL PROTECTED]> wrote:
> > --- [EMAIL PROTECTED] wrote:
> > > Is there something that the SQLite core can do better?
> >
> > Perhaps exclusive locks on journal files would help avoid this problem.
> > Or are the -journal and etilqs_* files supposed to
Hi,
Am Samstag, 10. März 2007 13:26 schrieb [EMAIL PROTECTED]:
> purpose. Where do I find out more about "anonymous mapped
> objects" for windows?
ot sure if this is what John wanted to suggest:
http://msdn2.microsoft.com/en-us/ms810613.aspx
Note that you can create a mapping using the systems
Joe Wilson <[EMAIL PROTECTED]> wrote:
> --- [EMAIL PROTECTED] wrote:
> > Is there something that the SQLite core can do better?
>
> Perhaps exclusive locks on journal files would help avoid this problem.
> Or are the -journal and etilqs_* files supposed to be sharable by other
> sqlite processes?
John Stanton <[EMAIL PROTECTED]> wrote:
> A suggestion for the journal files would be to make them private
> anonymous mapped objects.
The main purpose of the journal is so that if the program
or OS crashes or there is a power failure, once the machine
reboots and some other process tries to rea
A suggestion for the journal files would be to make them private
anonymous mapped objects. That works on both Unix and Windows and any
other POSIX compatible system. Then the journals would be impervious to
outside interference.
With Unix the mapped object has a fixed size so there would nee
--- [EMAIL PROTECTED] wrote:
> Is there something that the SQLite core can do better?
Perhaps exclusive locks on journal files would help avoid this problem.
Or are the -journal and etilqs_* files supposed to be sharable by other
sqlite processes?
http://www.backupassist.com/BackupAssist/faq.ht
[EMAIL PROTECTED] wrote:
J. Edgar Hoover
R. Buckminster Fuller
F. Scott Fitzgerald
T. Woodrow Wilson
H. Ross Perot
F. Lee Bailey
C. Everett Koop
L. Ron Hubbard
G. Gordon Liddy
S. Truett Cathy
S. Epatha Merkerson
and so forth...
And I do have a Ph.D. from Duke University :-)
So to be accurat
[EMAIL PROTECTED] wrote,
Gunnar Roth <[EMAIL PROTECTED]> wrote:
> Dr Hipp,
>
Nice to see that i am not the only one you read drh as Dr. H. ;-) in
fact his name is D. Richard Hipp.
But i have never seen before the habit to abreviate the first surname.
J. Edgar Hoover
R. Buckminster Fuller
Dave Dyer <[EMAIL PROTECTED]> wrote:
> In general, it's known that daemon processes such as antivirus
> and backup programs can unexpectedly have the journal file open,
> and interfere with sqlite. If you're deploying sqlite to enduser's
> machines, you can't change this.
>
> Absent a real solut
Gunnar Roth <[EMAIL PROTECTED]> wrote:
>
> > Dr Hipp,
> >
>
> Nice to see that i am not the only one you read drh as Dr. H. ;-) in
> fact his name is D. Richard Hipp.
> But i have never seen before the habit to abreviate the first surname.
>
J. Edgar Hoover
R. Buckminster Fuller
F. Scott Fi
Doesn't have to be .db3, but there are certain extension to avoid as posted.
RBS
-Original Message-
From: Allan, Mark [mailto:[EMAIL PROTECTED]
Sent: 09 March 2007 16:52
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] journal - "Unable to open the database file"
RB
ington D.C. metro area. If interested
contact [EMAIL PROTECTED]
-Original Message-
From: Allan, Mark [mailto:[EMAIL PROTECTED]
Sent: Friday, March 09, 2007 11:52 AM
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] journal - "Unable to open the database file"
RB Smissaert,
The da
"Allan, Mark" <[EMAIL PROTECTED]> wrote:
> RB Smissaert,
> The database file is named .vdb. Is .vdb ok or wrong? Does it =
> have to be .db3? Or is there just certian extensions I need to avoid?
>
> Dr Hipp,
> Currently all journals have been deleted by admin, so I am currently =
> trying to creat
Allan, Mark schrieb:
RB Smissaert,
The database file is named .vdb. Is .vdb ok or wrong? Does it have to
be .db3? Or is there just certian extensions I need to avoid?
I quote from http://www.sqlite.org/cvstrac/wiki?p=PerformanceTuningWindows
"Be *VERY, VERY* careful what you name your dat
you.
> -Original Message-
> From: RB Smissaert [mailto:[EMAIL PROTECTED]
> Sent: 09 March 2007 16:40
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] journal - "Unable to open the database file"
>
>
> If I remember well this is a problem if you
If I remember well this is a problem if you have the extension .db for the
database file and I think if you change that to something like .db3 then it
won't happen.
RBS
-Original Message-
From: Allan, Mark [mailto:[EMAIL PROTECTED]
Sent: 09 March 2007 16:23
To: sqlite-users@sqlite.org
Su
"Allan, Mark" <[EMAIL PROTECTED]> wrote:
> 3) Ask if anyone can offer any advise us as to what we can do
> to get around the problem of a journal file being locked and
> SQLite cannot delete it? Because at the moment if this situation
> occurs no one can write to that Db until the journal file h
26 matches
Mail list logo
