Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Tweaks to the documentation. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
b1eb2ef05f67f4cbf7b4532c24602603 |
| User & Date: | drh 2013-12-30 19:24:41 |
Context
|
2013-12-31
| ||
| 14:34 | Use the automatically generated file hierarchy tree rather than a separate static file. check-in: a8a1e64c57 user: drh tags: trunk | |
|
2013-12-30
| ||
| 19:24 | Tweaks to the documentation. check-in: b1eb2ef05f user: drh tags: trunk | |
| 14:48 | Add the comment "Modified to support SQLite extensions by the SQLite developers: sqlite-dev@sqlite.org." to the top of all files in this project that were copied from Android and then modified. check-in: 9c379550fd user: dan tags: trunk | |
Changes
Changes to www/index.wiki.
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
...
181
182
183
184
185
186
187
188
189
190
191
192
|
<p>instead of: <verbatim> android.database.SQLException android.database.DatabaseErrorHandler </verbatim> <p>Aside from namespace differences, there are only two differences from the stock Android interface that applications need to be aware of: <ol> <li> The SQLiteStatement.<a href="http://developer.android.com/reference/android/database/sqlite/SQLiteStatement.html#simpleQueryForBlobFileDescriptor()">simpleQueryForBlobFileDescriptor()</a> API is not available. <li> The collation sequence "UNICODE" is not available. Additionally, the collation sequence "LOCALIZED", which normally changes with the system's current locale, is always equivalent to SQLite's built in collation BINARY. </ol> <h2>Using The Simple Encryption Extension</h2> <p> To use the <a href=http://www.sqlite.org/see/doc/trunk/www/readme.wiki> Simple Encryption Extension</a> (SEE) on Android, replace the sqlite3.c file at "jni/sqlite/sqlite3.c" with a SEE-enabled version (i.e. the concatenation of sqlite3.c and see.c - refer to the link above for details). Next, open the file jni/sqlite/Android.mk and locate the following two lines: <verbatim> # If using SEE, uncomment the following: ................................................................................ is indistinguishable from opening a file that is not a database file. And it seems too dangerous to simply delete the file in this case. <br><br> The default behaviour can be overriden using the <a href="http://developer.android.com/reference/android/database/DatabaseErrorHandler.html">DatabaseErrorHandler</a> interface. </ol> |
|
|
>
|
|
|
<
<
<
<
<
|
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
...
182
183
184
185
186
187
188
|
<p>instead of: <verbatim> android.database.SQLException android.database.DatabaseErrorHandler </verbatim> <p>Aside from namespace changes, there are other differences from the stock Android interface that applications need to be aware of: <ol> <li> The SQLiteStatement.<a href="http://developer.android.com/reference/android/database/sqlite/SQLiteStatement.html#simpleQueryForBlobFileDescriptor()">simpleQueryForBlobFileDescriptor()</a> API is not available. <li> The collation sequence "UNICODE" is not available. <li> The collation sequence "LOCALIZED", which normally changes with the system's current locale, is always equivalent to SQLite's built in collation BINARY. </ol> <h2>Using The SQLite Encryption Extension</h2> <p> To use the <a href=http://www.sqlite.org/see/doc/trunk/www/readme.wiki> SQLite Encryption Extension</a> (SEE) on Android, replace the sqlite3.c file at "jni/sqlite/sqlite3.c" with a SEE-enabled version (i.e. the concatenation of sqlite3.c and see.c - refer to the link above for details). Next, open the file jni/sqlite/Android.mk and locate the following two lines: <verbatim> # If using SEE, uncomment the following: ................................................................................ is indistinguishable from opening a file that is not a database file. And it seems too dangerous to simply delete the file in this case. <br><br> The default behaviour can be overriden using the <a href="http://developer.android.com/reference/android/database/DatabaseErrorHandler.html">DatabaseErrorHandler</a> interface. </ol> |