System.Data.SQLite

Login
This project makes use of Eagle, provided by Mistachkin Systems.
Eagle: Secure Software Automation
2015-05-19
18:25 Closed ticket [7c151a2f0e]: UseUTF16Encoding=True creates a db with UTF-8 encoding plus 5 other changes artifact: 6b1e04c3b6 user: mistachkin
18:24
Make sure enabling UseUTF16Encoding sets the schema encoding to UTF-16. Fix for [7c151a2f0e]. check-in: 749d5af8d3 user: mistachkin tags: trunk
16:37 Ticket [7c151a2f0e] UseUTF16Encoding=True creates a db with UTF-8 encoding status still Open with 7 other changes artifact: eee5ad293c user: mistachkin
13:37 New ticket [7c151a2f0e]. artifact: 8f8730acad user: anonymous

Ticket Hash: 7c151a2f0e22804c36105462ac1e6c597678d048
Title: UseUTF16Encoding=True creates a db with UTF-8 encoding
Status: Closed Type: Code_Defect
Severity: Important Priority: Medium
Subsystem: Integration_Via_PInvoke Resolution: Fixed
Last Modified: 2015-05-19 18:25:39
Version Found In: 1.0.96.0
User Comments:
anonymous added on 2015-05-19 13:37:52:
I believe I found a regression in 1.0.96.0
Version 1.0.96.0 creates a db with (pragma) encoding=UTF-8 if UseUTF16Encoding=True, but a db with encoding=UTF-16le should be created instead.
Tested with sqlite-netFx451-static-binary-bundle-Win32-2013-1.0.96.0.zip.

The last known good version is 1.0.94.0 which creates a db with encoding UTF-16le.

mistachkin added on 2015-05-19 16:37:31:
I've managed to reproduce the issue locally.  Working on root diagnosis and fix.

mistachkin added on 2015-05-19 18:25:39:
Fixed on trunk via check-in [749d5af8d3197c94].  This fix will appear in the
1.0.97.0 release.