Re: [sqlite] output problem

On 5 Sep 2010, at 11:01am, Mark wrote: > a new problem regarding this. Got it to work fine with your help, on an sqb > database, trying to do the same with a db3 but it doesn't want to play. I > don't particularily need it to dump anything, I just need a file, any file, > to be created as

[sqlite] output problem

Hi there, a new problem regarding this. Got it to work fine with your help, on an sqb database, trying to do the same with a db3 but it doesn't want to play. I don't particularily need it to dump anything, I just need a file, any file, to be created as a trigger / signal to another part of

Re: [sqlite] output problem

On 14 Jun 2010, at 1:53pm, Mark wrote: > thanks, yeah sorry, what I meant to ask was, because the .read command is > going away to read another file, > away from this one, if you know what I mean, does it > actually know to wait for that to finish, or once it's started > executing the .read,

[sqlite] output problem

thanks, yeah sorry, what I meant to ask was, because the .read command is going away to read another file, away from this one, if you know what I mean, does it actually know to wait for that to finish, or once it's started executing the .read, does it immediately move on to the dump?

Re: [sqlite] output problem

: sqlite-users-boun...@sqlite.org on behalf of Mark Sent: Mon 6/14/2010 12:26 AM To: sqlite-users@sqlite.org Subject: [sqlite] output problem Hello, re-visiting this, thanks for the previous help, just a question on timing. Do the commands execute in order, that is, does the .read finish before

[sqlite] output problem

Hello, re-visiting this, thanks for the previous help, just a question on timing. Do the commands execute in order, that is, does the .read finish before the .output / .dump starts. It's a timing issue where the programme is waiting on the creation of the dump as a signal to finish, but the

Re: [sqlite] output problem

On 2 Jun 2010, at 1:09pm, CDN Mark wrote: > thanks Michael, my typing 2 forward slashes wasn't intentional, I realized > after I posted what I'd done, but it's good to know I can a forward slash > instead, so as long it it just goes to the C drive and no further, it should > be OK for all

Re: [sqlite] output problem

: "Black, Michael (IS)" <michael.bla...@ngc.com> To: "General Discussion of SQLite Database" <sqlite-users@sqlite.org>; "General Discussion of SQLite Database" <sqlite-users@sqlite.org> Sent: Wednesday, June 02, 2010 1:04 PM Subject: Re: [sqlite] output p

Re: [sqlite] output problem

to the root of C: drive. Michael D. Black Senior Scientist Northrop Grumman Mission Systems From: sqlite-users-boun...@sqlite.org on behalf of CDN Mark Sent: Wed 6/2/2010 6:48 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] output problem

Re: [sqlite] output problem

; <sqlite-users@sqlite.org> Sent: Wednesday, June 02, 2010 11:55 AM Subject: Re: [sqlite] output problem On 1 June 2010 12:52, Mark <m.co...@virgin.net> wrote: > Hi, > > trying to use .output to write a small text file, and send it to the C > drive. It looks like this: > &

Re: [sqlite] output problem

On 1 June 2010 12:52, Mark wrote: > Hi, > > trying to use .output to write a small text file, and send it to the C drive. >  It looks like this: > > .read UnPop.sql > .output C:\done.txt > .dump dbinfo > .quit > > works fine if I send it to the E drive, but as soon as I try

[sqlite] output problem

Hi, trying to use .output to write a small text file, and send it to the C drive. It looks like this: .read UnPop.sql .output C:\done.txt .dump dbinfo .quit works fine if I send it to the E drive, but as soon as I try anywhere on the C, whether to the drive itself, or a folder on C, it just