Skip to content

Mkauf fix utf8 supplementary characters#67

Merged
xerial merged 3 commits intomasterfrom
mkauf-fix-utf8-supplementary-characters
Oct 26, 2015
Merged

Mkauf fix utf8 supplementary characters#67
xerial merged 3 commits intomasterfrom
mkauf-fix-utf8-supplementary-characters

Conversation

@xerial
Copy link
Owner

@xerial xerial commented Oct 26, 2015

For testing #66

mkauf and others added 3 commits October 26, 2015 17:25
JNI uses a modified UTF-8 encoding. For supplementary characters, an invalid UTF-8 sequence was written to the database, which resulted in interoperability problems. The solution is to avoid UTF-8 in the native code and use the UTF-16 functions of SQLite (where possible). SQLite will then convert the UTF-16 to standards-compliant, unmodified UTF-8.

This also fixes related bugs in JDBC3PreparedStatement and improves the "out of memory" handling in the native code.

Fixed Issues:
- https://bitbucket.org/xerial/sqlite-jdbc/issues/200/wrong-utf-8-decoding-of-unicode-code , same as #61
- https://bitbucket.org/xerial/sqlite-jdbc/issues/144/nativedbexec-throws-an-exception-without
- https://bitbucket.org/xerial/sqlite-jdbc/issues/84/bug-in-nativedbc-bind_1blob
- https://bitbucket.org/xerial/sqlite-jdbc/issues/70/setting-a-blob-in-prepstmt
xerial added a commit that referenced this pull request Oct 26, 2015
…cters

Mkauf fix utf8 supplementary characters
@xerial xerial merged commit 1d91c24 into master Oct 26, 2015
@gotson gotson deleted the mkauf-fix-utf8-supplementary-characters branch August 12, 2022 07:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments