Talk:SQLite
From Wikipedia, the free encyclopedia
[edit] Criticisms
While I personally very much like SQLite, one of its major drawbacks (in my opinion, which is of course not neutral) is that it does not do any type checking. That means, if you insert 'hello' into an int column... it will not complain, and it will insert it just fine.
This is of course on purpose, and it is stated on the site why this is done, but I think it should be noted in this article - just as MySQL has criticisms.
-[Unknown] 18:39, Oct 11, 2004 (UTC)
[edit] Since SQLite 3 types are handled quite well
http://sqlite.org/datatype3.html : "In order to maximize compatibility between SQLite and other database engines, SQLite support the concept of "type affinity" on columns."
[edit] Link broken
SQLite C++ Wrapper (Target: http://cmk.navorski.com/index.php?wiki=Changelog) is redirected to casino onlinegames or something. I have removed the link. Please add the right one again.
[edit] Mutlithread deadlock problem with Temporary tables
After some time of consideration, I believe the multi-thread deadlock problem with temporary tables still needed to be addressed in the paragraph that concerns concurrent access issue. First, the paragraph beforehand does relate to concurrent access. Second, the target of SQLite users are aiming for performance and are likely exploiting the temporary table feature. This is not some casual bug reporting but a deadlock issue that will affect many SQLite users and relevant to the paragraph in question. The morale that Wikipedia is not bugzilla is well taken, but this problem will cause the system to deadlock which is fatal, and deserves to be properly addressed for anyone reading about SQLite. --Zero0w 05:02, 5 April 2006 (UTC)
- Given that it's now been fixed for two months and two releases (the article is out of date, I'll update it in a sec) I have to agree it isn't worthy of inclusion in this article. But, honestly, it doesn't bother me one way or the other very much. Still, it seems reasonable that if two months is not long enough that we quantify what *is* long enough. --Steven Fisher 02:18, 6 April 2006 (UTC)
-
- Ok, you suggested that a defined period of time to clarify the mention of the issue in question is interesting. Still since the previous paragraph is related to concurrent access, that was the reason I added the fix of concurrent access for temporary table in the first place. For the period, I'll suggest three months or two point releases later than the fix version to be safe enough to omit such information.
- The morale of mentioning this was two fold: (1) For those who tried SQLite but rejected it due to the bug, can try it again. (2) The concurrent access issue has been there in the first place and I figured people would think it works okay all along from the impression of the paragraph, yet this piece of information is relevant to them at the time of writing. And btw, I don't know a new version is out until your edit :P . --Zero0w 17:05, 6 April 2006 (UTC)
- I didn't either! I went to look to see when the issue was fixed. :) --Steven Fisher 06:21, 7 April 2006 (UTC)
[edit] Yum Performance Improvement Citation
"According to feedback from users, the performance improvement is impressive with reduced memory consumption as well.[citation needed]"
This isn't from "users" but I found: https://lists.dulug.duke.edu/pipermail/yum-devel/2005-January/000472.html —Preceding unsigned comment added by 199.245.163.1 (talk • contribs)
[edit] Removing Products using SQLite
I propose that the section about products using SQLite be removed. It really doesn't add useful information to the article, it does not provide nearly a complete list, and it's starting to look like a list of spam. Does anyone have comments on this? Beethoven05 22:18, 15 December 2006 (UTC)
- There's a very few on that list that add somewhat to the article, but the list keeps growing beyond that. I agree; it should be axed. --Steven Fisher 18:50, 18 December 2006 (UTC)
- The article should make a more prominent mention of how widespread SQLite use is, R. Hipp was quoted as saying it's probably the most used database engine worldwide, and there is little doubt about that as it's present on most of the PC (Apple, MS or Linux) and also made use of in large number of electronic appliances (as embedded db). 82.229.207.75 09:15, 12 July 2007 (UTC)
[edit] Language bindings
I noticed today that the language bindings were removed some time ago. Unlike the products list, the language bindings are actually useful. For instance, sqlite being part of the core install of Mac OS X is very relevant to the article. The large number of languages/frameworks that have added support for sqlite speaks volumes about its acceptance. On the other hand, it being part of Amarok is completely irrelevent. --Steven Fisher 00:04, 20 April 2007 (UTC)
Is it worth adding that there is an SqlLite ADO.NET provider for C# / VB.NET? Makes it as easy as dealing with an MsSql or SqlCe DB. —Preceding unsigned comment added by 83.105.22.250 (talk) 10:14, 7 January 2008 (UTC)
[edit] DISQLite3
I'm not happy with the DISQLite3 mentions in this article. A Wikipedia article shouldn't be used to advertise a lesser-known and mostly irrelevant product. If DISQLite3 merits its own article on wikipedia, let's create one and do a See Also link there Otherwise, I don't think it merits mention here either. --Steven Fisher 00:50, 25 June 2007 (UTC)
[edit] Author
While D. Richard Hipp is undoubtadly the main developer, I'm wondering if we should list Hwaci as the developer. Hwaci is the company that "employs the architect and principal developers of SQLite." DRH isn't the only person working on the code anymore. Thoughts? --Steven Fisher 18:02, 20 September 2007 (UTC)
[edit] Relevant SQLite tutorial - Why remove it?
souptonuts.sourceforge.net/readme_sqlite_tutorial.html This is an informative tutorial for users investigating SQLite, and it would serve users to have this link posted. As to whether or the article should be posted, take into consideration that it may serve users. Agreed, I'm the author of this article; but, that fact is independent of its usefulness to users.
My goal, and only goal in posting, as well as writing this article, is to provide information to users seeking to understand SQLite. I receive no royalties, no site promotion, or no personal benefit in anyway.
I do not understand why the link has to be removed because I'm the author. If the link is relevant, it should stay. Can putting the link on the site be evaluated on the content and relevance of the article alone? Why does posting have to first be prejudiced by who posts the article before it is evaluated? Please explain.
Regards,
Mike Chirico —Preceding unsigned comment added by Mchirico (talk • contribs) 23:30, 24 January 2008 (UTC)
- The messages I left on your talk page, and the text in WP:EL (see my edit summaries) should have been pretty clear. Adding sites you are affiliated with is not allowed, period. Your only contributions to Wikipedia consisted of adding links to your website. You have been blocked.[1] Han-Kwang (t) 00:45, 25 January 2008 (UTC)
-
-
- I still don't think it's necessary to included tutorial links on articles, but I'm not going to edit war about it. Chris Cunningham (talk) 19:29, 25 January 2008 (UTC)
-
[edit] Products using sqlite is back, only now it's called Adoption.
There's another list of products of varying notability here. Has anything changed since last time it was decided to remove this? --Steven Fisher (talk) 00:35, 29 February 2008 (UTC)
[edit] Pronunciation
How is SQLite pronounced? Sequlite, S Q Lite, S Q L Lite or all of the above? Mathiastck (talk) 19:40, 10 April 2008 (UTC)
- Watch the Introduction to SQLite video. It sounds like he's saying S Q Lite, but he's very fast. :) --Steven Fisher (talk) 00:03, 11 April 2008 (UTC)
[edit] SQLite and servers
"SQLite engine is not a standalone process with which the program communicates." (start of the article). Since there are servers that support SQlite for their hosted website, I wonder is this remains true? Macaldo (talk) 15:50, 22 April 2008 (UTC)
- It's still true. Combining the SQLite engine with something else doesn't change the nature of the engine. Steven Fisher (talk) 00:04, 25 April 2008 (UTC)
[edit] Comparison to libdb/Berkeley DB
Hi Sdfisher, you removed the reference to Berkeley DB under "see also" with the comment "other dbs don't need to be listed here, that's what categories are for". Sure, lots of DBMS are listed there, including Berkeley DB. However, IMHO Berkeley DB deserves special mention because it is very similar to sqlite, but this fact gets lost in the noise of the many other listed DBMS. Anyone interested in sqlite should be made aware of closely related efforts; basically, Berkeley DB is also a library, but does not have an SQL frontend, just an API for direct access to B trees which contain binary data. Please consider re-adding the "see also" entry! Stachelfisch (talk) 19:10, 30 May 2008 (UTC)
- I don't think just adding to the SA section is a good idea, but this is an interesting argument. Can you think of a way to fit it into the main article text in some section or another? --Steven Fisher (talk) 21:36, 3 June 2008 (UTC)
- Been thinking about this. Maybe we should start a history section for sqlite, since it was originally (I think?) built on BDB. I haven't got the time at the moment to find references to back up a history, though... --Steven Fisher (talk) 17:02, 9 June 2008 (UTC)