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 a trigger / signal to another part of the programme that the > INSERT / DELETE or UPDATE has been completed What happens if you try to ATTACH DATABASE on a file that doesn't exist ? Also, since you just need a simple signalling system, why not instead make a change to a file that does exist, and have the other program watch the modification date of that file ? Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[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 the programme that the INSERT / DELETE or UPDATE has been completed mtia Mark ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
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, does it immediately move on to the > dump? The command-line tool does not call another utility to process the '.read' command, it has to do all the work itself. Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[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? ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] output problem
The command-line interface is not multi-threaded so it all executes in sequence. I can't imagine how many questions/problems would be on this list if it were multi-threaded...yikes!! Michael D. Black Senior Scientist Northrop Grumman Mission Systems From: 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 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 .read could take maybe 10 seconds or more. .read UnPop.sql .output C:\done.txt .dump dbinfo .quit mtia Mark ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[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 .read could take maybe 10 seconds or more. .read UnPop.sql .output C:\done.txt .dump dbinfo .quit mtia Mark ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
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 users? You should be able to specify any reasonable path or folder, using backslashes. I think that your problem was that the user didn't have write access to the default folder on 'C:', so specifying just 'C:filename' lead to a write error'. It is actually usual to have access to the root directory, so using just 'C:\filename' is probably a bad idea. You're going to have to figure out just where you really want your file to be saved. Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] output problem
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 users? Mark - Original Message - From: "Black, Michael (IS)" To: "General Discussion of SQLite Database" ; "General Discussion of SQLite Database" Sent: Wednesday, June 02, 2010 1:04 PM Subject: Re: [sqlite] output problem > Inside code you can use forward slash for path seperators (dang Microsoft > for ever introducing this backslash stuff). > > so this works on ALL windows operating systems that I know of > .output c:/done.txt > > Note though that if your user doesn't have admin priveledges they may not > be able to write 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 > > > > thanks Simon, that worked, why is this? and if I wanted to send this to > someone else and it had the // would it NOT work for them? > > Mark > - Original Message - > From: "Simon Davies" > To: "General Discussion of SQLite Database" > Sent: Wednesday, June 02, 2010 11:55 AM > Subject: 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 anywhere on >> the C, whether to the drive itself, or a folder on C, it just doesn't >> work >> at all, >> nothing is created. I do need it it to go to at least the C drive, and >> preferably a folder on C > > looks like Windoze - double up your '\' chars, > > i.e. > > .output C:\\done.txt > >> >> mtia, >> Mark > > Regards, > Simon > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] output problem
Inside code you can use forward slash for path seperators (dang Microsoft for ever introducing this backslash stuff). so this works on ALL windows operating systems that I know of .output c:/done.txt Note though that if your user doesn't have admin priveledges they may not be able to write 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 thanks Simon, that worked, why is this? and if I wanted to send this to someone else and it had the // would it NOT work for them? Mark - Original Message - From: "Simon Davies" To: "General Discussion of SQLite Database" Sent: Wednesday, June 02, 2010 11:55 AM Subject: 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 anywhere on > the C, whether to the drive itself, or a folder on C, it just doesn't work > at all, > nothing is created. I do need it it to go to at least the C drive, and > preferably a folder on C looks like Windoze - double up your '\' chars, i.e. .output C:\\done.txt > > mtia, > Mark Regards, Simon ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] output problem
thanks Simon, that worked, why is this? and if I wanted to send this to someone else and it had the // would it NOT work for them? Mark - Original Message - From: "Simon Davies" To: "General Discussion of SQLite Database" Sent: Wednesday, June 02, 2010 11:55 AM Subject: 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 anywhere on > the C, whether to the drive itself, or a folder on C, it just doesn't work > at all, > nothing is created. I do need it it to go to at least the C drive, and > preferably a folder on C looks like Windoze - double up your '\' chars, i.e. .output C:\\done.txt > > mtia, > Mark Regards, Simon ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
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 anywhere on the > C, whether to the drive itself, or a folder on C, it just doesn't work at all, > nothing is created. I do need it it to go to at least the C drive, and > preferably a folder on C looks like Windoze - double up your '\' chars, i.e. .output C:\\done.txt > > mtia, > Mark Regards, Simon ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[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 doesn't work at all, nothing is created. I do need it it to go to at least the C drive, and preferably a folder on C mtia, Mark ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
