Re: [sqlite] Formatting SQLite-query
Maybe yes. I am currently looking into parameterized queries. Is it like this: sqlite_prepare sqlite_bind_* sqlite_finalize with the query like 'SELECT * FROM ? WHERE ? = ?'... But how can I know what I pass? I mean with %d/%s/... It's rather obvious, but how do I know what I pass when I use those parameters... And this project has been put aside for a while until I find a solution for this problem (it's the only thing keeping me from completing the program :p). But I have still other things to do ;-). Thanks for any help! At 21:35 1/11/2004, you wrote: Steven Van Ingelgem said: > > Sorry but this has already been suggested by "Tiago Dionizio". > > I can use this, but then I have to create some kind of own printf-function > which scans and so on and handles %q's (which is rather dumb in my > opinion, > as SQLite already incorporates it?). > > > I think this is a va_* error but I am unable to determine the exact > source... Your issue then is less with SQLite and more with C++ programming. Your error message might be showing up deep in the SQLite library, but the problem occurs in your handling of the parameters. I would advise you not to let your project get held up on the %Q issue, since the escaping you need to do is pretty trivial. Also consider that SQLite 3 allows you to use parameterized queries, which eliminates the need for the escaping anyway. -- Lazarus Notes from Lazarus Internet Development http://www.lazarusid.com/notes/ Articles, Reviews and Commentary on web development KaReL (aka Steven) Main Webpage : http://www.karels0ft.be/ ICQ # : 35217584 pgp6uvnhC8wCR.pgp Description: PGP signature
Re: [sqlite] Release / development timeline
D Richard Hipp wrote: > How much more announcing do you think we should do? The timeline page is great, for finding out when things were done. Changes is great for saying what is in the new versions, and when they were released How about a simple page that gives projected release date for upgrades? Something like Version 3.0.9 beta 10 November Version 3.0.9 final 20 November Version 3.0.10 beta 1 December Version 3.0.10 final 15 December xan jonathon -- How to have Hittite, Alibata, Orkhon, Ogham, Manchu, Meroïtic, Pahawh Hmong, Tengwar, Tsalagi, Hangul, Lepcha, and Nushu in the same document. http://oooauthors.org/groups/members/tutorials/
Re: [sqlite] Release / development timeline
Gerry Snyder wrote: I think version 3 becoming "stable" should be announced to the linux and TCL worlds, among many other places. This is a big thing! It was announced on freshmeat.net and I gave talks on 3.0 at OSCON 2004 and at the TclConference 2004. How much more announcing do you think we should do? Who is the appropriate spokesperson? Anyone but me :-) -- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
Re: [sqlite] Release / development timeline
Christian Smith wrote: Releases generally happen as and when bugs dictate. Now that 3.0.x is stable, I guess most releases for the next few months will be ongoing bug fixing. Plus minor feature additions, perhaps. Like having a default time as "now," as has already been discussed here. SQLite is a gem among the many fine examples of Open Source software. Gerry PS I think version 3 becoming "stable" should be announced to the linux and TCL worlds, among many other places. This is a big thing! Who is the appropriate spokesperson? -- -- Gerry Snyder AIS Director, Affiliates Chair, Symposium Chair in warm, winterless Los Angeles -- USDA zone 9b, Sunset 18-19
Re: [sqlite] Release / development timeline
On Mon, 1 Nov 2004, Jonathon Blake wrote: >All: > >I've hunted around on sqlite.org, and the mailing list archives, [and >googled] for a timeline of when the next version9s) of SqLite will be >released. > >Does such a critter exist, and if so, where can I find it? I don't think there is a roadmap as such, and so no timeline for releases. Releases generally happen as and when bugs dictate. Now that 3.0.x is stable, I guess most releases for the next few months will be ongoing bug fixing. > >xan > >jonathon > Christian -- /"\ \ /ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL X - AGAINST MS ATTACHMENTS / \
Re: [sqlite] new uploads
mike cariotoglou wrote: > I have uploaded the current version of sqlite3Explorer (a GUI to > manage sqlite3 databases) to http://www.sqlite.org/contrib. also, I Hi Mike, I was trying to use your sqlite3Explorer program to look at my database, but it won't open it. I get a dialog with the following error when I use File/Open Database... --- sqlite3explorer --- Could not convert variant of type (Null) into type (String) --- OK --- After this I am left with schema tree with only one table, the first one listed by the .schema command in sqlite3.exe. Using sqlite3.exe to dump the database shows all the tables actually exist (ther are 38) as well as their associated indexes and triggers. I'm using sqlite3.dll version 3.08 built from CVS source, and the version of sqlite3Explorer on the SQLite website. Any ideas? If you want I can send you a copy of the problematic database file. P.S. A little further digging shows that it is reading the database, only the schema tree view is not working. I can see all the tables with reasonable counts using the View/Show Tables with Counts command. Without the schema tree view working, I can't seem to display the contents of anything other than the master table, and this first table (which is empty).
[sqlite] Building SQLite in MSVC 6
Hello. First I'd like to compliment you on a very nice product; I've been adding database support to an open source project and SQLite is of immense help to us. I've been building SQLite as a library and as a DLL for Windows using Visual C++ 6 from sources of version 3.0.8. I'd be happy to publish or provide you with a .dsp (project file) for both types of compilation, as I couldn't seem to find them anywhere on the site. I've gotten quite a few warnings while compiling; one of the warnings is severe IMHO - the function access() used in shell.c has no prototype (an #include is needed there somewhere). There are lots of other warnings that can probably be removed. I was wandering if you would be fixing those warnings, or if you'd like me to try and fix them myself and send you the results. Guy
[sqlite] Release / development timeline
All: I've hunted around on sqlite.org, and the mailing list archives, [and googled] for a timeline of when the next version9s) of SqLite will be released. Does such a critter exist, and if so, where can I find it? xan jonathon -- How to have Hittite, Alibata, Orkhon, Ogham, Manchu, Meroïtic, Pahawh Hmong, Tengwar, Tsalagi, Hangul, Lepcha, and Nushu in the same document. http://oooauthors.org/groups/members/tutorials/
Re: [sqlite] Formatting SQLite-query
Steven Van Ingelgem said: > > Sorry but this has already been suggested by "Tiago Dionizio". > > I can use this, but then I have to create some kind of own printf-function > which scans and so on and handles %q's (which is rather dumb in my > opinion, > as SQLite already incorporates it?). > > > I think this is a va_* error but I am unable to determine the exact > source... Your issue then is less with SQLite and more with C++ programming. Your error message might be showing up deep in the SQLite library, but the problem occurs in your handling of the parameters. I would advise you not to let your project get held up on the %Q issue, since the escaping you need to do is pretty trivial. Also consider that SQLite 3 allows you to use parameterized queries, which eliminates the need for the escaping anyway. -- Lazarus Notes from Lazarus Internet Development http://www.lazarusid.com/notes/ Articles, Reviews and Commentary on web development
Re: [sqlite] Formatting SQLite-query
Sorry but this has already been suggested by "Tiago Dionizio". I can use this, but then I have to create some kind of own printf-function which scans and so on and handles %q's (which is rather dumb in my opinion, as SQLite already incorporates it?). I think this is a va_* error but I am unable to determine the exact source... At 20:07 1/11/2004, you wrote: Steven Van Ingelgem said: > Sorry to bump this up, but i was still not able to find an answer for > this > question :( > > http://www.wxwidgets.org/manuals/2.4.2/wx368.htm#wxstringformat Clay Dowling -- Lazarus Notes from Lazarus Internet Development http://www.lazarusid.com/notes/ Articles, Reviews and Commentary on web development KaReL (aka Steven) Main Webpage : http://www.karels0ft.be/ ICQ # : 35217584 pgpIki8qNIiOM.pgp Description: PGP signature
[sqlite] [ANN] rq-0.1.7
URLS http://raa.ruby-lang.org/project/rq/ http://www.codeforpeople.com/lib/ruby/rq/ NAME rq v0.1.7 SYNOPSIS rq (queue | export RQ_Q=q) mode [mode_args]* [options]* DESCRIPTION ruby queue (rq) is a tool used to create instant linux clusters by managing sqlite databases as nfs mounted priority work queues. multiple instances of rq running from multiples hosts can work from these queues to distribute processing load to n nodes - bringing many dozens of otherwise powerful cpus to their knees with a single blow. clearly this software should be kept out of the hands of free radicals, seti enthusiasts, and j. safran. the central concept of rq is that n nodes work in isolation to pull jobs from an central nfs mounted work priority work queue in a synchronized fashion. the nodes have absolutely no knowledge of each other and all communication if done via the queue meaning that, so long as the queue is available via nfs and a single node is running jobs from it, the system will continue to process jobs. there is no centralized process whatsoever - all nodes work to take jobs from the queue and run them as fast as possible. this creates a system which load balances automatically and is robust in face of node failures. the first argument to any rq command is the name of the queue. this name may be omitted if, and only if, the environment variable RQ_Q has been set to contain the absolute path of target queue. rq operates in one of the modes create, submit, list, status, delete, update, query, execute, configure, snapshot, lock, backup, help, or feed. depending on the mode of operation and the options used the meaning of 'mode_args' may change. MODES the following mode abbreviations exist c => create s => submit l => list ls => list t => status d => delete rm => delete u => update q => query e => execute C => configure S => snapshot L => lock b => backup h => help f => feed create, c : create a queue. the queue must be located on an nfs mounted file system visible from all nodes intended to run jobs from it. examples : 0) to create a queue ~ > rq /path/to/nfs/mounted/q create or simply ~ > rq /path/to/nfs/mounted/q c submit, s : submit jobs to a queue to be proccesed by a feeding node. any 'mode_args' are taken as the command to run. note that 'mode_args' are subject to shell expansion - if you don't understand what this means do not use this feature and pass jobs on stdin. when running in submit mode a file may by specified as a list of commands to run using the '--infile, -i' option. this file is taken to be a newline separated list of commands to submit, blank lines and comments (#) are allowed. if submitting a large number of jobs the input file method is MUCH, more efficient. if no commands are specified on the command line rq automatically reads them from STDIN. yaml formatted files are also allowed as input (http://www.yaml.org/) - note that the output of nearly all rq commands is valid yaml and may, therefore, be piped as input into the submit command. when submitting the '--priority, -p' option can be used here to determine the priority of jobs. priorities may be any whole number - zero is the default. note that submission of a high priority job will NOT supplant currently running low priority jobs, but higher priority jobs WILL always migrate above lower priority jobs in the queue in order that they be run as soon as possible. constant submission of high priority jobs may create a starvation situation whereby low priority jobs are never allowed to run. avoiding this situation is the responsibility of the user. the only guaruntee rq makes regarding job execution is that jobs are executed in an 'oldest highest priority' order and that running jobs are never supplanted. examples : 0) submit the job ls to run on some feeding host ~ > rq q s ls 1) submit the job ls to run on some feeding host, at priority 9 ~ > rq -p9 q s ls 2) submit 42000 jobs (quietly) from a command file. ~ > wc -l cmdfile 42000 ~ > rq q s -q < cmdfile 3) submit 42 priority 9 jobs from a command file. ~ > wc -l cmdfile 42 ~ > rq -p9 q s < cmdfile 4) submit 42 priority 9 jobs from a command file, marking them as 'important' using the '--tag, -t' option. ~ > wc -l cmdfile 42 ~ > rq -p9 -timportant q s < cmdfile 5) re-submit all the 'important' jobs (see 'query' section below) ~ > rq q query tag=important | rq q s 6) re-submit all jobs which are already finished (see 'list' section below) ~ > rq q l f | rq q s list, l, ls : list mode lists jobs of a certain state or job id.
Re: [sqlite] Formatting SQLite-query
Steven Van Ingelgem said: > Sorry to bump this up, but i was still not able to find an answer for > this > question :( > > http://www.wxwidgets.org/manuals/2.4.2/wx368.htm#wxstringformat Clay Dowling -- Lazarus Notes from Lazarus Internet Development http://www.lazarusid.com/notes/ Articles, Reviews and Commentary on web development
Re: [sqlite] php: src/auth.c:128: sqliteAuthRead: Assertion `pStack!=0' failed.
Per Jessen wrote: I'm running a small php-script in command-line mode - initially everything goes fine until a table in the db reaches around 8700 rows, then I see the assert failing. This is 2.8.15, which I'm using with PHP4.3.8/SQLite-1.0.3. I don't believe I'm doing anything overly complicated - lots of inserts, the occasional update. This is probably the same as ticket #896 which is fixed in the CVS tree. See: http://www.sqlite.org/cvstrac/tktview?tn=896 -- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
[sqlite] php: src/auth.c:128: sqliteAuthRead: Assertion `pStack!=0' failed.
I'm running a small php-script in command-line mode - initially everything goes fine until a table in the db reaches around 8700 rows, then I see the assert failing. This is 2.8.15, which I'm using with PHP4.3.8/SQLite-1.0.3. I don't believe I'm doing anything overly complicated - lots of inserts, the occasional update. any help appreciated! /Per -- regards, Per Jessen, Zurich http://www.spamchek.com - let your spam stop here!
