Documentation Source Text

Check-in [c34168d55b]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:There are "hundreds of billions", not "tens of billions" of SQLite database files in circulation - in the rowidtable.html document.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:c34168d55b39d1002c0eeb27c342a0bf8e953e4adbecb33274701ae0bee54df8
User & Date: drh 2018-04-12 15:31:42
Context
2018-04-12
17:04
Fix a typo on the optoverview.html document. check-in: 5272d8d61d user: drh tags: trunk
15:31
There are "hundreds of billions", not "tens of billions" of SQLite database files in circulation - in the rowidtable.html document. check-in: c34168d55b user: drh tags: trunk
14:47
Tweaks to the whynotgit.html page. check-in: 149486cfb5 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/rowidtable.in.

62
63
64
65
66
67
68
69
70
71
72
73
74
75
[variable-length integer].  That means that small non-negative
rowid values take up less disk space than large or negative
rowid values.

<li><p>
All of the complications above (and others not mentioned here)
arise from the need to preserve backwards
compatibility to the tens of billions of SQLite database files in
circulation.  In a perfect world, there would be no such thing as a "rowid"
and all tables would following the standard semantics implemented as
[WITHOUT ROWID] tables, only without the extra "WITHOUT ROWID" keywords.
Unfortunately, life is messy.  The designer of SQLite offers his
sincere apology for the current mess.
</ul>







|






62
63
64
65
66
67
68
69
70
71
72
73
74
75
[variable-length integer].  That means that small non-negative
rowid values take up less disk space than large or negative
rowid values.

<li><p>
All of the complications above (and others not mentioned here)
arise from the need to preserve backwards
compatibility for the hundreds of billions of SQLite database files in
circulation.  In a perfect world, there would be no such thing as a "rowid"
and all tables would following the standard semantics implemented as
[WITHOUT ROWID] tables, only without the extra "WITHOUT ROWID" keywords.
Unfortunately, life is messy.  The designer of SQLite offers his
sincere apology for the current mess.
</ul>