[sqlite] Fwd: Re: sqlite journal file question

On 2/14/2015 12:19 AM, Mayank Kumar (mayankum) wrote: > Thanks all for the responses. Just want to clarify the scenario one more > time:- > > -by syncing, I mean taking the modifications on the active machine and > sending over wire to another machine(in some proprietary format) , where >

[sqlite] sqlite journal file question

On 13 Feb 2015, at 10:19pm, Mayank Kumar (mayankum) wrote: > -by syncing, I mean taking the modifications on the active machine and > sending over wire to another machine(in some proprietary format) , where > there is a similar sqlite application which receives the records and the > records

[sqlite] sqlite journal file question

] On Behalf Of R.Smith Sent: Friday, February 13, 2015 1:15 AM To: sqlite-users at sqlite.org Subject: Re: [sqlite] sqlite journal file question This was my initial reading too Paul, but reading the OP post again it could be either - who knows what is meant by "syncing". I also think this i

[sqlite] sqlite journal file question

On 2/13/15, Mayank Kumar (mayankum) wrote: > when we > do a rsync, does it make sense to copy the journal file Yes, yes. Emphatically, Yes. -- D. Richard Hipp drh at sqlite.org

Re: [sqlite] sqlite journal file question

This was my initial reading too Paul, but reading the OP post again it could be either - who knows what is meant by "syncing". I also think this is the main point for the OP - If by syncing he really means "copying the file" then Richard's advice, else if he means "adding via normal DB

Re: [sqlite] sqlite journal file question

Richard I read that the db on the standby machine is being updated at a record by record level, i.e. not copied in its entirety. In this scenario I can't see the two db files being guaranteed binary compatible. Copying the journal across in this scenario would imo be a mistake. Paul

Re: [sqlite] sqlite journal file question

On 2/12/15, Mayank Kumar (mayankum) wrote: > Hi All > > We have two systems which are running in active/standby configuration. The > active machine, is actively writing sqlite transactions to a file abcd.db. > The standby is syncing the abcd.db file from the active machine

Re: [sqlite] sqlite journal file question

I don't think it can be done, and if it could be done, it would not be wise. The journal is owned and specific to a connection. a hot Journal for connection A on DB 1 cannot ever be used to roll back or affect in any way connection B on DB 2. However, when you say the "standby is syncing", I

Re: [sqlite] sqlite journal file question

I would say no. The journal file stores pages referenced by page no and when replayed will write those pages back to the main DB at the appropriate physical offset. Although the content of your DB's at a logical level may be the same, it is unlikely that they will be exact copies at a binary level

[sqlite] sqlite journal file question

Hi All We have two systems which are running in active/standby configuration. The active machine, is actively writing sqlite transactions to a file abcd.db. The standby is syncing the abcd.db file from the active machine on a communication channel and writing the delta records to the

Re: [sqlite] Journal file question

On 4/19/07, Joe Wilson <[EMAIL PROTECTED]> wrote: --- DragonK <[EMAIL PROTECTED]> wrote: > I'm having the following problem: a sqlite database file is on an NTFS > filesystem, in a directory with no permissions to create new files, but only > to modify the original database. By using filemon

Re: [sqlite] Journal file question

--- DragonK <[EMAIL PROTECTED]> wrote: > I'm having the following problem: a sqlite database file is on an NTFS > filesystem, in a directory with no permissions to create new files, but only > to modify the original database. By using filemon i've noticed some access > denied errors when sqlite

Re: [sqlite] Journal file question

On 4/18/07, Cesar Rodas <[EMAIL PROTECTED]> wrote: I think is imposible... what you need to do is to create a dbname.db-journalform a dbname.db and set permission to truncate, write, but not for delete.. that is what i suggest, but i didnt try it... If you're suggesting to create a dummy

Re: [sqlite] Journal file question

I think is imposible... what you need to do is to create a dbname.db-journalform a dbname.db and set permission to truncate, write, but not for delete.. that is what i suggest, but i didnt try it... On 18/04/07, DragonK <[EMAIL PROTECTED]> wrote: Hi, I'm having the following problem: a

[sqlite] Journal file question

Hi, I'm having the following problem: a sqlite database file is on an NTFS filesystem, in a directory with no permissions to create new files, but only to modify the original database. By using filemon i've noticed some access denied errors when sqlite attempted to create the journal files.