Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Add a mising link to index.wiki. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
8b4072a7dbfc9a470b5363f99907db61 |
| User & Date: | dan 2013-12-25 18:56:39 |
Context
|
2013-12-25
| ||
| 19:03 | Move c/c++ code into the jni/sqlite/ sub-directory. To make it easier to copy into other projects. check-in: 938b5766d5 user: dan tags: trunk | |
| 18:56 | Add a mising link to index.wiki. check-in: 8b4072a7db user: dan tags: trunk | |
| 17:50 | Add some documentation files. check-in: 67c837ca6c user: dan tags: trunk | |
Changes
Changes to www/index.wiki.
164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 |
Refer to the <a href=http://www.sqlite.org/see/doc/trunk/www/readme.wiki>
SEE documentation</a> for further details regarding encryption keys.
<p>Aside from supporting encrypted databases, SEE-enabled builds behave
differently in two more respects:
<ol>
<li> <p>The SQLiteDatabase.enableWriteAheadLogging() method does not enable
connection pooling. It is not possible for connection pooling to be
used with a SEE-enabled build (even if the database is unencrypted).
<li> <p>In Android, if database corruption is encountered, or if an attempt is
made to open a file that is not an SQLite database, the default
behaviour is to delete the file and create an empty database file in
its place. In a SEE-enabled build, the default behaviour is to throw
|
| |
164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 |
Refer to the <a href=http://www.sqlite.org/see/doc/trunk/www/readme.wiki> SEE documentation</a> for further details regarding encryption keys. <p>Aside from supporting encrypted databases, SEE-enabled builds behave differently in two more respects: <ol> <li> <p>The SQLiteDatabase.<a href="http://developer.android.com/reference/android/database/sqlite/SQLiteDatabase.html#enableWriteAheadLogging()">enableWriteAheadLogging()</a> method does not enable connection pooling. It is not possible for connection pooling to be used with a SEE-enabled build (even if the database is unencrypted). <li> <p>In Android, if database corruption is encountered, or if an attempt is made to open a file that is not an SQLite database, the default behaviour is to delete the file and create an empty database file in its place. In a SEE-enabled build, the default behaviour is to throw |