Re: [sqlite] Can multi-column index optimize my operation?
On Thu, 2009-08-13 at 23:39 -0400, Igor Tandetnik wrote: > Kermit Mei wrote: > > The mostly useful SQL sentence is (MyDevId is known by user): > > > > SELECT * FROM KeyItem WHERE HomeDevId=MyDevId order by pageNum; > > > > Now, the items of this table may be more than 100,000 lines. If I use > > the following Index, can it improve the previous query's speed? > > > > CREATE INDEX index_KeyItem_HP ON KeyItem(HomeDevId, pageNum ASC); > > Yes, this should help. > > > I use index firstly, so I don't know how to manipulate it? Just > > create a index like this, or any more operation is needed? > > No, just creating the index should be enough. SQLite should use it > automatically if it's beneficial for a particular query. > > Igor Tandetnik Yes, I see. Thank you, Tandetnik. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Can multi-column index optimize my operation?
Kermit Mei wrote: > The mostly useful SQL sentence is (MyDevId is known by user): > > SELECT * FROM KeyItem WHERE HomeDevId=MyDevId order by pageNum; > > Now, the items of this table may be more than 100,000 lines. If I use > the following Index, can it improve the previous query's speed? > > CREATE INDEX index_KeyItem_HP ON KeyItem(HomeDevId, pageNum ASC); Yes, this should help. > I use index firstly, so I don't know how to manipulate it? Just > create a index like this, or any more operation is needed? No, just creating the index should be enough. SQLite should use it automatically if it's beneficial for a particular query. Igor Tandetnik ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Can multi-column index optimize my operation?
Hello, I have I table like this: CREATE TABLE KeyItem (icon_y int, icon_x int, id INTEGER PRIMARY KEY, pos_x int, pos_y int, size_x int, size_y int, type int, text varchar(15), icon varchar(50), background varchar(50), HomeDevId int, pageNum int); The mostly useful SQL sentence is (MyDevId is known by user): SELECT * FROM KeyItem WHERE HomeDevId=MyDevId order by pageNum; Now, the items of this table may be more than 100,000 lines. If I use the following Index, can it improve the previous query's speed? CREATE INDEX index_KeyItem_HP ON KeyItem(HomeDevId, pageNum ASC); I use index firstly, so I don't know how to manipulate it? Just create a index like this, or any more operation is needed? Thanks Kermit Mei ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Error 14 - SQLITE_CANTOPEN
2009/8/13 Simon Slavin: > > On 13 Aug 2009, at 12:47pm, Otto Grunewald wrote: > >> on the website at the following address: >> >> http://www.sqlite.org/c3ref/exec.html >> >> The second paragraph states the following: >> >> The error message passed back through the 5th parameter is held in >> memory obtained from sqlite3_malloc(). To avoid a memory leak, the >> calling application should call sqlite3_free() on any error message >> returned through the 5th parameter when it has finished using the >> error >> message. > > I raised this question a couple of weeks ago. It would be nice to > have a very clear definition of when you need to use _free. For > instance is it exactly when _exec doesn't return SQLITE_OK ? If _step > returns SQLITE_BUSY, does that mean there's an error message to be > freed ? If I call _free when there's no error, would that be a > problem ? > > Simon. I set errmsg arg passed in to _exec to 0. If it is changed after exec, then I call _free Rgds, Simon ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLite version 3.6.17
On Thu, 13 Aug 2009, Mike Frysinger wrote: > On Thursday 13 August 2009 12:25:39 Hugh Sasse wrote: > > Well, I've found out why the tests aren't included in the amalgamated > > version. I think it is because it has taken over 5 hours to run the full > > test suite on the Solaris9 box I have, and they are not finished yet. I've > > not noticed any failures yet though; hopefully I can give a report > > tomorrow. > > the size/length of the testsuite shouldnt have any bearing on including it. > testsuites exist for a reason. also, the current situation is that there is > no *nix release that is "supported" that includes a testsuite. > -mike I should have put a :-) in there. There is a quick test option, which I didn't use, aiming to report useful results. But I expect the usual ./configure && make && make check taking over 5 hours would be a bit of a shock for most people! It's nice to see several groups with thousands of tests in, though. > Hugh ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLJet - pure Java implementation of SQLite
Our approach in the 1980s was to make the compiler. Interestingly you mention a Databus to C product wich did not flourish (as one would expect for a translator).. We produced a complete Databus compiler to a target code like Java. This product sold well and is still viable thanks to the large base of legacy Databus source. The virtual machine, like the Java VM was implemented on many architectures and would run the target code unchanged, like Java. All this predated Java and found use with OEMs distributing applications across many architectures as well as with outfits preserving their legacy ptograms. Native code implementations were merely a matter of making a native code generator for the compiler backend. Fred Williams wrote: > I think you are talking "Open Source" world now. In the late 80's, early > 90's things like Open Source Databas/Datashare compilers weren't even in > anyone's dreams. What you saw was what you got. With no open source > compilers to monkey with you just did what you had to, pretty or not. > > Somebody did later write a Databus/Datashare to C translator and the > Datapoint world beat a very deep pathway to his door! Shortly after that > Datapoint was no more and his market evaporated. > > Sorry, this ain't SQLite at all. I'm done here. > > Fred > > -Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of John Stanton > Sent: Thursday, August 13, 2009 1:32 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] SQLJet - pure Java implementation of SQLite > > > In this situation it has been our approach to never try to translate > source in one language into another. It is a pointlesss activity when > you think about it. Much better to have the C or whatever compiler have > a different code generator, for example Java target code. > > You are not rev locked that way and if your C compiler optimizes well > you have an efficient executable. Your JIT compiler still works. > > People would spend months translating program into error ridden monsters > instead of spending less time working on a compiler and ending up with > unchanged source with no added errors and which can be easily maintained > in the origibal code with the comments still meaningful. > > Fred Williams wrote: > >> Having had the unfortunate opportunity to use a couple of language >> translators as well as spending about six fruitless months developing one >> which in the end was no better, I say there is no known translation that >> would allow the three SQLite, "Small, Fast, Reliable" adjectives to >> translate into any regurgitated language output, with the exception of >> compiling SQLite source with a C++ compiler :-) >> >> Fred >> >> -Original Message- >> From: sqlite-users-boun...@sqlite.org >> [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of Roger Binns >> Sent: Tuesday, August 11, 2009 7:15 PM >> To: General Discussion of SQLite Database >> Subject: Re: [sqlite] SQLJet - pure Java implementation of SQLite >> >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Alexander Kitaev wrote: >> >> >>> Not to depend on native SQLite binaries or >>> opaque NestedVM code, >>> >>> >> As a matter of interest what problem exactly do you have with NestedVM? >> It's output is indeed opaque (not human comprehensible) but the same is >> > true > >> of Java source versus bytecode. In both cases the input source is >> > readable. > >> It would also be interesting if anyone has built something that >> > comprehends > >> the SQLite C source and then does the conversion into other languages >> > based > >> on that. It would make updates a lot easier, the generation of >> > instrumented > >> and test code easier, and the search for issues or optimisations easier. >> >> Roger >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.9 (GNU/Linux) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> >> iEYEARECAAYFAkqCCWgACgkQmOOfHg372QQXqwCeJ4pqKa89vcCAxTQOelMyoPU6 >> cuQAoK6Feey6AL3pdzMgv983tn8Yg1ML >> =TKoq >> -END PGP SIGNATURE- >> ___ >> 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 > ___ sqlite-users mailing list sqlite-users@sqlite.org
Re: [sqlite] SQLJet - pure Java implementation of SQLite
I think you are talking "Open Source" world now. In the late 80's, early 90's things like Open Source Databas/Datashare compilers weren't even in anyone's dreams. What you saw was what you got. With no open source compilers to monkey with you just did what you had to, pretty or not. Somebody did later write a Databus/Datashare to C translator and the Datapoint world beat a very deep pathway to his door! Shortly after that Datapoint was no more and his market evaporated. Sorry, this ain't SQLite at all. I'm done here. Fred -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of John Stanton Sent: Thursday, August 13, 2009 1:32 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] SQLJet - pure Java implementation of SQLite In this situation it has been our approach to never try to translate source in one language into another. It is a pointlesss activity when you think about it. Much better to have the C or whatever compiler have a different code generator, for example Java target code. You are not rev locked that way and if your C compiler optimizes well you have an efficient executable. Your JIT compiler still works. People would spend months translating program into error ridden monsters instead of spending less time working on a compiler and ending up with unchanged source with no added errors and which can be easily maintained in the origibal code with the comments still meaningful. Fred Williams wrote: > Having had the unfortunate opportunity to use a couple of language > translators as well as spending about six fruitless months developing one > which in the end was no better, I say there is no known translation that > would allow the three SQLite, "Small, Fast, Reliable" adjectives to > translate into any regurgitated language output, with the exception of > compiling SQLite source with a C++ compiler :-) > > Fred > > -Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of Roger Binns > Sent: Tuesday, August 11, 2009 7:15 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] SQLJet - pure Java implementation of SQLite > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Alexander Kitaev wrote: > >> Not to depend on native SQLite binaries or >> opaque NestedVM code, >> > > As a matter of interest what problem exactly do you have with NestedVM? > It's output is indeed opaque (not human comprehensible) but the same is true > of Java source versus bytecode. In both cases the input source is readable. > > It would also be interesting if anyone has built something that comprehends > the SQLite C source and then does the conversion into other languages based > on that. It would make updates a lot easier, the generation of instrumented > and test code easier, and the search for issues or optimisations easier. > > Roger > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkqCCWgACgkQmOOfHg372QQXqwCeJ4pqKa89vcCAxTQOelMyoPU6 > cuQAoK6Feey6AL3pdzMgv983tn8Yg1ML > =TKoq > -END PGP SIGNATURE- > ___ > 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] SQLJet - pure Java implementation of SQLite
In this situation it has been our approach to never try to translate source in one language into another. It is a pointlesss activity when you think about it. Much better to have the C or whatever compiler have a different code generator, for example Java target code. You are not rev locked that way and if your C compiler optimizes well you have an efficient executable. Your JIT compiler still works. People would spend months translating program into error ridden monsters instead of spending less time working on a compiler and ending up with unchanged source with no added errors and which can be easily maintained in the origibal code with the comments still meaningful. Fred Williams wrote: > Having had the unfortunate opportunity to use a couple of language > translators as well as spending about six fruitless months developing one > which in the end was no better, I say there is no known translation that > would allow the three SQLite, "Small, Fast, Reliable" adjectives to > translate into any regurgitated language output, with the exception of > compiling SQLite source with a C++ compiler :-) > > Fred > > -Original Message- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of Roger Binns > Sent: Tuesday, August 11, 2009 7:15 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] SQLJet - pure Java implementation of SQLite > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Alexander Kitaev wrote: > >> Not to depend on native SQLite binaries or >> opaque NestedVM code, >> > > As a matter of interest what problem exactly do you have with NestedVM? > It's output is indeed opaque (not human comprehensible) but the same is true > of Java source versus bytecode. In both cases the input source is readable. > > It would also be interesting if anyone has built something that comprehends > the SQLite C source and then does the conversion into other languages based > on that. It would make updates a lot easier, the generation of instrumented > and test code easier, and the search for issues or optimisations easier. > > Roger > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkqCCWgACgkQmOOfHg372QQXqwCeJ4pqKa89vcCAxTQOelMyoPU6 > cuQAoK6Feey6AL3pdzMgv983tn8Yg1ML > =TKoq > -END PGP SIGNATURE- > ___ > 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] Error 14 - SQLITE_CANTOPEN
On 13 Aug 2009, at 12:47pm, Otto Grunewald wrote: > on the website at the following address: > > http://www.sqlite.org/c3ref/exec.html > > The second paragraph states the following: > > The error message passed back through the 5th parameter is held in > memory obtained from sqlite3_malloc(). To avoid a memory leak, the > calling application should call sqlite3_free() on any error message > returned through the 5th parameter when it has finished using the > error > message. I raised this question a couple of weeks ago. It would be nice to have a very clear definition of when you need to use _free. For instance is it exactly when _exec doesn't return SQLITE_OK ? If _step returns SQLITE_BUSY, does that mean there's an error message to be freed ? If I call _free when there's no error, would that be a problem ? Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLite version 3.6.17
Well, I've found out why the tests aren't included in the amalgamated version. I think it is because it has taken over 5 hours to run the full test suite on the Solaris9 box I have, and they are not finished yet. I've not noticed any failures yet though; hopefully I can give a report tomorrow. Thank you Hugh ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] [Delphi] Reading list of tables?
That's all you are suppose to get when querying the Master table for table names. You ask how to get a list of tables. That is what you got. What you are asking for now is more complex. Try: Select Name, SQL from "SQLite_master"; for even more fun try: Select * from "SQLite_master" Fred -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]on Behalf Of Gilles Ganault Sent: Thursday, August 13, 2009 3:28 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] [Delphi] Reading list of tables? On Tue, 11 Aug 2009 11:35:16 +0100, Simon Slavinwrote: >SELECT sql FROM sqlite_master WHERE type='table' Thanks Simon. To get only the name of the tables instead of the SQL command that was used to create them: SELECT tbl_name FROM sqlite_master WHERE type="table"'; ___ 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] Sqlite in multithread application fails the update query.
I have tested an archive under a multithread (32) application. Every thread appends a new record in a unique table. After the thread updates only own records. On exit the thread verifies that all own records are be updated but somethimes some records are not be updated correctly. The insert and update query is under transaction and no exception are be generated. This behaviour happens under Linux and under Windows. If you want the source or compiled program for Windows and Linux please send me an email. Sorry for my bad english. -- Denis Gottardello Sintesi S.r.l. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Error 14 - SQLITE_CANTOPEN
Otto Grunewald wrote: > When an error message is returned by sqlite3_exec the documentation > states that you have to call sqlite3_free (sqlite3_free(void*)). > > My question is the following: > > Where do I get the void pointer from? You do sqlite3_free(errmsg), of course. Igor Tandetnik ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Error 14 - SQLITE_CANTOPEN
Hello, It is on the website at the following address: http://www.sqlite.org/c3ref/exec.html The second paragraph states the following: The error message passed back through the 5th parameter is held in memory obtained from sqlite3_malloc(). To avoid a memory leak, the calling application should call sqlite3_free() on any error message returned through the 5th parameter when it has finished using the error message. Regards, Otto -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of D. Richard Hipp Sent: 13 August 2009 13:41 To: General Discussion of SQLite Database Subject: Re: [sqlite] Error 14 - SQLITE_CANTOPEN On Aug 13, 2009, at 7:27 AM, Otto Grunewald wrote: > > When an error message is returned by sqlite3_exec the documentation > states that you have to call sqlite3_free (sqlite3_free(void*)). > That sounds like a bug in the documentation. Where are you seeing this, exactly. I can't find it anywhere. D. Richard Hipp d...@hwaci.com ___ 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] Error 14 - SQLITE_CANTOPEN
On Aug 13, 2009, at 7:27 AM, Otto Grunewald wrote: > > When an error message is returned by sqlite3_exec the documentation > states that you have to call sqlite3_free (sqlite3_free(void*)). > That sounds like a bug in the documentation. Where are you seeing this, exactly. I can't find it anywhere. D. Richard Hipp d...@hwaci.com ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Error 14 - SQLITE_CANTOPEN
Hello, I apologize for posting the message on the development mailing list. Yes, it was a mistake in transcribing the code : the line actually looks like this: sqlite3_open("/var/ptudata/ptu.db", _handle); I think I found the problem though. If you have a look at the while loop it was coded incorrectly by the previous developer of the system. If the table is locked by another process the sqlite3_exec will through an error. With the while loop we retry 100 times to execute the query before breaking out of the loop. But in the example it will break out after only doing it once. I am currently retesting will keep you up to date. Maybe you can assist with another problem. When an error message is returned by sqlite3_exec the documentation states that you have to call sqlite3_free (sqlite3_free(void*)). My question is the following: Where do I get the void pointer from? Regards Otto -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of D. Richard Hipp Sent: 13 August 2009 13:08 To: General Discussion of SQLite Database Subject: Re: [sqlite] Error 14 - SQLITE_CANTOPEN On Aug 13, 2009, at 5:30 AM, Otto Grunewald wrote: > Hello, > The following is what my code looks like : > sqlite3 *db_handle; > char* errmsg; > char cStr(255); > > sqlite3_open(_handle); > sqlite3_open() takes two parameters. Did you make a mistake in transcribing your code? D. Richard Hipp d...@hwaci.com ___ 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] 'database locked' error
Hello, I would like to pass cookies back and forth between a search script I have written that runs on the local system, and javascript pages displaying the forms and results in Firefox. I'll forego all the gory details here, it is working pretty well, but being able to pass cookies back and forth would make allow me to make it much more robust. FF (3+) uses an sqlite db to store it's cookies. I have tried to edit cookie values using sqlite3, but I keep getting a 'database locked' error, incessantly. (Does FF simply put a lock on this file at the beginning of a session and not release it til it is done?) I have read things that talk about using fcntl() to get around this, but it is quite over my head, though I am willing to invest, as I really want to accomplish this. If I could get some suggestions on how to handle this situation to my ends, I would much appreciate it. I could just simply copy the db file, alter the cookie values, and then copy it over the existing cookies db. This works. Perhaps a more kosher way would be to use fcntl() (or something) to get a mandatory exclusive lock beforehand. This is an area I am quite unfamiliar with, but willing to invest in learning if it seems feasible. I really would like to be able to edit the cookies outside of FF and I believe there is a way without just forcing it. Reading them is no problem, but I want to be able to write flags back to the javascript while it is running. Perhaps copying over the db file is not such a big deal, after all, this would (most likely) only be occurring while the user is using the search feature anyway. Any thoughts on this? But if I can do this in a more kosher manner, it would be better. Any input on this? Thanks much, Allasso -- View this message in context: http://www.nabble.com/%27database-locked%27-error-tp24953225p24953225.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Error 14 - SQLITE_CANTOPEN
On Aug 13, 2009, at 5:30 AM, Otto Grunewald wrote: > Hello, > The following is what my code looks like : > sqlite3 *db_handle; > char* errmsg; > char cStr(255); > > sqlite3_open(_handle); > sqlite3_open() takes two parameters. Did you make a mistake in transcribing your code? D. Richard Hipp d...@hwaci.com ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLite version 3.6.17
On Thu, 13 Aug 2009, Dan Kennedy wrote: > On Aug 13, 2009, at 4:58 PM, Hugh Sasse wrote: > > > Thanks. I think even if they don't change this, and they clearly > > have reasons for how things are, then clarity about maintenance > > would be useful. > > It works at present. It is tested informally before each release. > But support could be dropped at any time. The problem is that at > this time there exists no individual capable of and willing to make > the commitment to maintain it. The current version is not up to > date with the newer autoconf stuff either. That would seem to be worth adding to the website, or maybe just the sentence "This distribution needs a maintainer". > > Dan. > Thank you, Hugh ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLite version 3.6.17
On Aug 13, 2009, at 4:58 PM, Hugh Sasse wrote: > On Thu, 13 Aug 2009, Mike Frysinger wrote: > >> On Thursday 13 August 2009 05:04:26 Hugh Sasse wrote: >>> On Wed, 12 Aug 2009, Mike Frysinger wrote: On Monday 10 August 2009 11:51:40 Hugh Sasse wrote: > Make check doesn't do anything. My reading of Makefile{,.in,.am} > suggests this is intended. I was wondering if being able run the > full tests on various possibly obscure architectures would be > useful. the tests are removed from the amalgamation tarball. you have to get the full tarball for the tests. >>> >>> OK, but for that there are warnings in bold about not doing that >>> unless you >>> must, and I'm not clear whether "The Makefile and configure script >>> in this tarball are not supported." means they are not maintained, >>> or means >>> you just can't [guarantee to] get help if stuck. >> >> ive complained in the past about this situation, but doesnt seem >> like there's >> much (any) interest in resolving things. i was merely giving you >> details >> about how to actually/easily run the tests with the current release. > > Thanks. I think even if they don't change this, and they clearly > have reasons for how things are, then clarity about maintenance > would be useful. It works at present. It is tested informally before each release. But support could be dropped at any time. The problem is that at this time there exists no individual capable of and willing to make the commitment to maintain it. The current version is not up to date with the newer autoconf stuff either. Dan. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLite version 3.6.17
On Thu, 13 Aug 2009, Mike Frysinger wrote: > On Thursday 13 August 2009 05:04:26 Hugh Sasse wrote: > > On Wed, 12 Aug 2009, Mike Frysinger wrote: > > > On Monday 10 August 2009 11:51:40 Hugh Sasse wrote: > > > > Make check doesn't do anything. My reading of Makefile{,.in,.am} > > > > suggests this is intended. I was wondering if being able run the > > > > full tests on various possibly obscure architectures would be useful. > > > > > > the tests are removed from the amalgamation tarball. you have to get the > > > full tarball for the tests. > > > > OK, but for that there are warnings in bold about not doing that unless you > > must, and I'm not clear whether "The Makefile and configure script > > in this tarball are not supported." means they are not maintained, or means > > you just can't [guarantee to] get help if stuck. > > ive complained in the past about this situation, but doesnt seem like there's > much (any) interest in resolving things. i was merely giving you details > about how to actually/easily run the tests with the current release. Thanks. I think even if they don't change this, and they clearly have reasons for how things are, then clarity about maintenance would be useful. For example, would they like patches for the configure scripts? I'm probably too involved with other things to do much for a while anyway, but I generally like to contribute something back to projects I use if I can. Thanks again. > -mike > Hugh ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Error 14 - SQLITE_CANTOPEN
Hello, The following is what my code looks like : sqlite3 *db_handle; char* errmsg; char cStr(255); sqlite3_open(_handle); while (sqlite3_exec(db_handle, cStr, NULL, 0, ) != SQLITE_OK) { printf("sqlite3_exec: %s - retry cnt: %i\n", sqlite3_errmsg(db_handle), ++cnt); if (cnt > 100) break; usleep(5); break; } sync(); sqlite3_close(db_handle); The problem I'm having is the following. After doing this a thousand (1000) times consecutively the sqlite3_exec function throws the following error : SQLITE_CANTOPEN14 /* Unable to open the database file */ Does anybody know what the cause of this problem might be? Am I using the correct functions? Some assistance would be greatly appreciated. Regards, Otto Grünewald ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Proprietary versus Open source ETL tools
Hi, As of today, we are still enjoying our Informatica tool but in a few months we will need to change. Basically we do not use our software at its full capacity and don't feel we need it anymore. So we are trying to find a less expensive solution that would have the same features (or almost...). We are looking at less expensive tools and Open source software. We have pretty much targeted a few companies and would like to know which ones would be the better solution compared to Informatica. -Apatar -Expressor -Pentaho -Talend Some are paying software, some are open source (but not free...), so i'm asking you to know which is the best software on the market. Thanks. -- View this message in context: http://www.nabble.com/Proprietary-versus-Open-source-ETL-tools-tp24951790p24951790.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLite version 3.6.17
On Wed, 12 Aug 2009, Mike Frysinger wrote: > On Monday 10 August 2009 11:51:40 Hugh Sasse wrote: > > On Mon, 10 Aug 2009, D. Richard Hipp wrote: > > > SQLite version 3.6.17 is now available on the SQLite website: > > [...] > > > This is the first release of SQLite after 100% branch test coverage of > > > the SQLite core was achieved. The effort to bring SQLite up to 100% > > > > Sounds good to me! :-) > > > > Make check doesn't do anything. My reading of Makefile{,.in,.am} > > suggests this is intended. I was wondering if being able run the > > full tests on various possibly obscure architectures would be useful. > > the tests are removed from the amalgamation tarball. you have to get the > full > tarball for the tests. OK, but for that there are warnings in bold about not doing that unless you must, and I'm not clear whether "The Makefile and configure script in this tarball are not supported." means they are not maintained, or means you just can't [guarantee to] get help if stuck. I might give it a spin when I get a bit of time, anyway. > -mike > Thank you, Hugh ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] SQLJet - pure Java implementation of SQLite
En/na Simon Slavin ha escrit: > We no longer have the heritage of ubiquitous high-level languages. > Fortran, Pascal, Structured Basic, and everything like that have > gone. I don't know about the situation of fortran right now and I don't really care about basic, but pascal is alive and kicking and highly portable: http://www.freepascal.org Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 (Ext.133) Fax +34 93 5883007 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] [Delphi] Reading list of tables?
On Tue, 11 Aug 2009 11:35:16 +0100, Simon Slavinwrote: >SELECT sql FROM sqlite_master WHERE type='table' Thanks Simon. To get only the name of the tables instead of the SQL command that was used to create them: SELECT tbl_name FROM sqlite_master WHERE type="table"'; ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users