Talk:SQLite

This is the talk page for discussing improvements to the SQLite article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Archives: Index, 1: 365 days

Computing: Software / Free and open-source software Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Mid-importance).
	This article is supported by Free and open-source software (assessed as Mid-importance).

Databases (inactive)

This article is within the scope of WikiProject Databases, a project which is currently considered to be inactive.DatabasesWikipedia:WikiProject DatabasesTemplate:WikiProject DatabasesDatabases articles

Archives (index)

Index 1

This page has archives. Sections older than 365 days may be automatically archived by when more than 4 sections are present.

following MySql syntax, not postgres'

given postgresql follows mysql in doing automatic type conversions, and SQLite has AUTOINCREMENT, i suggest the text to be amended : SQLIte generally follows MySql's syntax — Preceding unsigned comment added by 2A01:E35:8A25:4D20:419B:56A9:5A22:16D7 (talk) 06:00, 15 June 2019 (UTC)[reply]

Intro goes on at length about a fairly minor technical detail?

In the intro section there is the following:

SQLite generally follows PostgreSQL syntax. SQLite uses a dynamically and weakly typed SQL syntax that does not guarantee the domain integrity.[7] This means that one can, for example, insert a string into a column defined as an integer. SQLite will attempt to convert data between formats where appropriate, the string "123" into an integer in this case, but does not guarantee such conversions and will store the data as-is if such a conversion is not possible.

This takes up almost half the introduction and to me seems like a technical detail that is not what the first thing I would bring up if someone asked me to describe what SQLite is. I'm nominating that for deletion, with the possibility of maybe making it stand out more in the design section, perhaps as a titled subsection. Thoughts? 24.228.172.139 (talk) 05:26, 19 January 2022 (UTC)[reply]

It could be discussed how much to emphasise and where exactly to put this, but outright deletion is way wild. This is not a "fairly minor technical detail", it's a huge issue.

Another huge issue is with the article itself: It's rather outdated in places. For instance, the above-mentioned "technical detail" has been largely fixed since November 2021 (IIRC), by using the keyword "strict" when creating a table. (This is mentioned in several other places in the article, most notably along the lines of "this was announced in 2015, but nothing has been heard since" [Quoted from memory].) -- CRConrad (talk) 10:35, 10 June 2022 (UTC)[reply]

Verification failed: Inclusion with Windows 10

I saw this in the article: "SQLite is included by default in: [...] Windows 10"

Sadly, whoever had written this was too careless with checking their source: [1] If you look at the source, however, you see that it recommends two options: Entity Framework and Microsoft.Data.Sqlite. Now, click on the "Microsoft.Data.Sqlite" link. (Here is a reproduction of that link: [2]) As you can see, the GitHub repo for this component has been shuttered. This project has been merged with Entity Framework. (See the Readme section of the repo.) Waysidesc (talk) 00:26, 7 February 2022 (UTC)[reply]

Grammar: 'a' vs. 'an' SQLite database

This article currently uses both 'a' and 'an' as the indefinite article when referring to 'SQLite database'. Which is correct depends on pronunciation, but it would probably be good to at least be consistent.

The official SQLite documentation uses 'an' exclusively from what I can tell [3], which is also consistent with the creator's pronunciation of "ess queue ell light" [4]. Willbicks (talk) 05:16, 14 July 2023 (UTC)[reply]

Fixed. I think 'an' makes more sense because "ess queue ell" seems like the official pronunciation, while "sequel" is just a shorthand people use. –CWenger (^ • @) 13:50, 15 July 2023 (UTC)[reply]