Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a typo. "databse" to "database". |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
eb3ea9a9536855666fcaa4731cbbbb94 |
| User & Date: | drh 2015-10-16 11:35:39 |
Context
|
2015-10-16
| ||
| 16:59 | Preliminary changes for the 3.9.1 patch release. (check-in: e2554ac473 user: drh tags: trunk) | |
| 11:35 | Fix a typo. "databse" to "database". (check-in: eb3ea9a953 user: drh tags: trunk) | |
|
2015-10-15
| ||
| 01:25 | Add a fragment for the ".dump" command in the cli.html documentation. (check-in: 2530eac4fe user: drh tags: trunk) | |
Changes
Changes to pages/versionnumbers.in.
13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
<p> All SQLite releases starting with 3.9.0 use a three-number "[http://semver.org|semantic version]" of the form X.Y.Z. The first number X is only increased when there is a change that breaks backward compatibility. The current value for X is 3, and the SQLite developers plan to support the current SQLite databse file format, SQL syntax, and C interface through at least the year 2050. Hence, one can expect that all future versions of SQLite for the next several decades will begin with "3.". <p> The second number Y is incremented for any change that breaks forward compatibility by adding new features. |
| |
13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
<p>
All SQLite releases starting with 3.9.0 use a three-number
"[http://semver.org|semantic version]" of the form X.Y.Z.
The first number X is only increased when there is a change that
breaks backward compatibility. The
current value for X is 3, and the SQLite developers plan to support
the current SQLite database file format, SQL syntax, and C interface
through at least the year 2050. Hence, one
can expect that all future versions of SQLite for the next several
decades will begin with "3.".
<p>
The second number Y is incremented for any change that breaks forward
compatibility by adding new features.
|