Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|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|
|User & Date:||drh 2018-04-12 15:31:42|
|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 to pages/rowidtable.in.
62 62 [variable-length integer]. That means that small non-negative 63 63 rowid values take up less disk space than large or negative 64 64 rowid values. 65 65 66 66 <li><p> 67 67 All of the complications above (and others not mentioned here) 68 68 arise from the need to preserve backwards 69 -compatibility to the tens of billions of SQLite database files in 69 +compatibility for the hundreds of billions of SQLite database files in 70 70 circulation. In a perfect world, there would be no such thing as a "rowid" 71 71 and all tables would following the standard semantics implemented as 72 72 [WITHOUT ROWID] tables, only without the extra "WITHOUT ROWID" keywords. 73 73 Unfortunately, life is messy. The designer of SQLite offers his 74 74 sincere apology for the current mess. 75 75 </ul>