Add BinaryGUID connection string to select binary/string GUID storage

[AlexanderTaeschner]

Addresses #273.

To be able to access the new BinaryGUID property in ConnectionStringBuilder from the parameter binding I added a wrapper around the sqlite3_stmt object and add the associated connection to it.

[bricelam]

This will greatly complicate any framework that generates SQL literals (including EFCore). I want to re-discuss with the team whether we should ever implement this feature.

[AlexanderTaeschner]

Please keep in mind, that this only affects the way an GUID parameter is bind. Since #191 is resolved, the library can read both binary and string GUID without being told how the data is stored (thanks to the dynamic type system of sqlite).

[bricelam]

Understood. Our philosophy so far has been to be highly compatible on reads, but highly predictable on writes. We support many formats when reading DateTime, DateTimeOffset, Guid, and TimeSpan values, but we'll always write using a canonical format.

Currently, EF Core generates queries like the following.

SELECT $someGuidParam = x'SOME_BLOB_VALUE';
-- or
SELECT * FROM MyTable
WHERE SomeGuidColumn = x'SOME_BLOB_VALUE';

After this, they'd return zero/empty, and we (EF Core and other libraries using this) would need to change the format of Guid literals based on the connection string.

[AlexanderTaeschner]

Ah okay, now I understand the problem.

[bricelam]

Closing. We decided against taking this feature.