Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | More typo fixes in quirks.html |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
f6681985cd814f13795d4f87dff09308 |
| User & Date: | drh 2019-07-11 16:31:53 |
Context
|
2019-07-13
| ||
| 16:24 | Remove obsolete and unsupported BNF and TEXT representations of the grammar. check-in: b02f76d76f user: drh tags: trunk | |
|
2019-07-11
| ||
| 16:31 | More typo fixes in quirks.html check-in: f6681985cd user: drh tags: trunk | |
| 16:01 | Fix typos in the quirks document. check-in: 596c4951a0 user: drh tags: trunk | |
Changes
Changes to pages/quirks.in.
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
...
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
If you are an SQLite user whose has stumbled over some quirk of SQLite that is not mentioned here, please send us an email so that we can document the problem. <h1>SQLite Is Embedded, Not Client-Server</h1> <p> When ever comparing SQLite to other SQL database engines like SQL Server, PostgreSQL, MySQL, or Oracle, it is important first of all to realize that SQLite is not intended as a replacement or competitor to any of those systems. SQLite is [serverless]. There is no separate server process that manages the database. An application interact with the database engine using function calls, not be sending messages to a separate process or thread. <p> The fact that SQLite is embedded and [serverless] instead of being client/server is a feature, not a bug. <p> ................................................................................ Which format you use, is entirely up to your application. <h1>Foreign Key Enforcement Is Off By Default</h1> <p>SQLite has parsed foreign key constraints for time out of mind, but added the ability to actually enforce those constraints much later, with [version 3.6.19] ([dateof:3.6.19]). By the time foreign key constraint enforcement was added, there where already countless millions of databases in circulation that contained foreign key constraints, some of which were not correct. To avoid breaking those legacy databases, foreign key constraint enforcement is turned off by default in SQLite. <p>Applications can activate foreign key enforcement at run-time using the [PRAGMA foreign_keys] statement. Or, foreign key enforcement can be activated at compile-time using the |
|
|
|
|
|
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
...
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
If you are an SQLite user whose has stumbled over some quirk of SQLite that is not mentioned here, please send us an email so that we can document the problem. <h1>SQLite Is Embedded, Not Client-Server</h1> <p> Whenever comparing SQLite to other SQL database engines like SQL Server, PostgreSQL, MySQL, or Oracle, it is important first of all to realize that SQLite is not intended as a replacement or competitor to any of those systems. SQLite is [serverless]. There is no separate server process that manages the database. An application interacts with the database engine using function calls, not by sending messages to a separate process or thread. <p> The fact that SQLite is embedded and [serverless] instead of being client/server is a feature, not a bug. <p> ................................................................................ Which format you use, is entirely up to your application. <h1>Foreign Key Enforcement Is Off By Default</h1> <p>SQLite has parsed foreign key constraints for time out of mind, but added the ability to actually enforce those constraints much later, with [version 3.6.19] ([dateof:3.6.19]). By the time foreign key constraint enforcement was added, there were already countless millions of databases in circulation that contained foreign key constraints, some of which were not correct. To avoid breaking those legacy databases, foreign key constraint enforcement is turned off by default in SQLite. <p>Applications can activate foreign key enforcement at run-time using the [PRAGMA foreign_keys] statement. Or, foreign key enforcement can be activated at compile-time using the |