SQLite4
Check-in [c0b7f14c09]
Not logged in
HomeTimelineBranchesTagsWikiLogin

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

Overview
Comment:Update the README into a README.md and clearly state that work on SQLite4 has concluded, lest there be any doubt.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: c0b7f14c0976ed5e0d1a7e3be1eb08bab7cd02d0
User & Date: drh 2017-10-27 15:49:12
Context
2019-05-29
13:35
Update the homepage to try to make it more clear that the SQLite4 effort has ended. check-in: 042b751618 user: drh tags: trunk
2017-10-27
15:49
Update the README into a README.md and clearly state that work on SQLite4 has concluded, lest there be any doubt. check-in: c0b7f14c09 user: drh tags: trunk
2016-07-28
13:44
Fix typo in the LSM documentation. check-in: c2d3bd7694 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Name change from README to README.md. 

1

2


3




4
5
6
7
8
9
10

This directory contains source code to 




    SQLite: An Embeddable SQL Database Engine





To compile the project, first create a directory in which to place
the build products.  It is recommended, but not required, that the
build directory be separate from the source directory.  Cd into the
build directory and then from the build directory run the configure
script found at the root of the source tree.  Then run "make".


|
>

>
>
|
>
>
>
>








1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

This directory contains source code to an experimental "version 4"
of SQLite that was being developed between 2012 and 2014.

<b>All development work on SQLite4 has ended.  The experiment has
concluded.</b>

Lessons learned from SQLite4 have been folded into SQLite3 which
continues to be actively maintained and developed.  This repository
exists as an historical record.
<b>There are no plans at this time to resume development of SQLite4.</b>

To compile the project, first create a directory in which to place
the build products.  It is recommended, but not required, that the
build directory be separate from the source directory.  Cd into the
build directory and then from the build directory run the configure
script found at the root of the source tree.  Then run "make".
︙︙