|This is the talk page for discussing improvements to the SQLite article.|
|Archives: Index, 1|
|This article is of interest to the following WikiProjects:|
|Threads older than 365 days may be archived by.|
sqlite3 is not just a standalone program, or what?
The article says that 'sqlite3 is a standalone program ...'. Isn't there a standalone program for every version? And for version 3 the stand alone program just happens to be called 'sqlite3'? I think it is misleading.
Could be nice too, if someone could comment on differences and compatibilities between versions.
Grammar for bindings statement in overview at top
Just a thought of grammar, should "It has many bindings to programming languages." be replaced with "It has bindings to many programming languages." or "It has bindings for many programming languages.". I believe the second and third statements are grammatically better, but I'm not sure whether it should be "bindings to" or "bindings for".
In the meantime, I have added a link to Language binding in the sentence in question.
Providing db as a library is common
Just read the opening paragraph ending with : "In contrast to other database management systems, SQLite is not a separate process that is accessed from the client application, but an integral part of it."
If the goal is to avoid useless hype, that kind of comparisons should be avoided. Even though a claim can be true at one point of time it most likely will not be true infinitely. Providing a db in a linked lib is common way to provide db functionality. There are various ways to implement this. Library can be static, or dynamic. The server can use shared memory so that clients can be run in separate processes and access the same data. I'm not aware how wide is the support of SQLite, but the centence could as well say 'Like most embedded database management systems ... Unlike most database management systems, SQLite doesn't give the opportunity to run in separate server process'. 188.8.131.52 (talk) 09:24, 6 July 2012 (UTC)
"This restriction is relaxed in version 3.7 when WAL is turned on enabling concurrent reads and writes."
The referenced articles does not support this assertion - it states:
1) WAL provides more concurrency as readers do not block writers and a writer does not block readers. Reading and writing can proceed concurrently. 2) Writers merely append new content to the end of the WAL file. Because writers do nothing that would interfere with the actions of readers, writers and readers can run at the same time. However, since there is only one WAL file, there can only be one writer at a time.