Closed prosconi closed 1 year ago
Since #71 was implemented and everything is separated out to their own namespace, I think it makes sense to add a Dapper.FSharp.SQLite namespace with a SQLite specific implementation.
Dapper.FSharp.SQLite
The new implementation can support INSERT OR REPLACE (see: https://www.sqlite.org/lang_conflict.html)
INSERT OR REPLACE
Example implementation of INSERT OR REPLACE
let! conflictCount = insert { orReplace into personsView values modified } |> conn.InsertAsync
Since SQLite does not support most data types, TypeHandlers should be created (see: https://learn.microsoft.com/en-us/dotnet/standard/data/sqlite/types)
TypeHandlers
I already have an implementation working locally.
Cool! Free feel to send a PR.
PR submitted
Perfect, will have a look!
Merged, tested, deployed - thanks for the great work!
Since #71 was implemented and everything is separated out to their own namespace, I think it makes sense to add a
Dapper.FSharp.SQLite
namespace with a SQLite specific implementation.The new implementation can support
INSERT OR REPLACE
(see: https://www.sqlite.org/lang_conflict.html)Example implementation of INSERT OR REPLACE
Since SQLite does not support most data types,
TypeHandlers
should be created (see: https://learn.microsoft.com/en-us/dotnet/standard/data/sqlite/types)I already have an implementation working locally.