Statement of compliance to Web SQL Database DRAFT API
brodybits opened this issue · 0 comments
Reference: https://www.w3.org/TR/webdatabase/
Quite a bit of work has already been done to test and document this but it is definitely not complete. Ideal would be a tested statement of compliance that goes through https://www.w3.org/TR/webdatabase/ in linear order and then through some other items including:
- SQLite (3) parameters (may be ?NNN, ?, :AAA, @AAAA, or $AAAA ref: https://www.sqlite.org/lang_expr.html#varparam and https://www.sqlite.org/c3ref/bind_blob.html) vs Web SQL
?
(ref: https://www.w3.org/TR/webdatabase/#parsing-and-processing-sql-statements) - Major features added after sqlite 3.6.19
- Extensions that may not be covered after sqlite 3.6.19
- General statement about other post-sqlite 3.6.19 features and other general SQLite features that may fall outside https://www.w3.org/TR/webdatabase/
- Comparison with the actual behavior of WebKit Web SQL on Android and iOS
It would also be nice to have this for https://github.com/nolanlawson/node-websql which is the basis for "SQLite Plugin 2" (ref: #547 Comparison with SQLite Plugin 2?)
P.S. Also a statement about why the DEPRECATED Web SQL Database DRAFT standard is used (portability of existing application code and libraries: developers were already using the API for web apps on Safari and Chrome; existence of excellent tutorials and other documentation; etc.)