Normally (when working in a non-Unity C# project), I would import a System.Data.SQLite.Core NuGet package (https://system.data.sqlite.org).
But I wasn't able to make it work in a Unity project (that would be a separate question I guess).
So, I ended up using the Mono.Data.Sqlite library, which is included in Unity (..\Editor\Data\MonoBleedingEdge\libmono\unityjit).
My question is: Are there any known disadvantages for this (for using the Mono library instead of System one)?
Thanks.
My target platform is Windows 64-bit only. Unity 2018.2.0f2 Scripting Runtime Version: .NET 4.x Equivalent Scripting Backend: Mono Api Compatibility Level: .NET 4.x
But I wasn't able to make it work in a Unity project (that would be a separate question I guess).
So, I ended up using the Mono.Data.Sqlite library, which is included in Unity (..\Editor\Data\MonoBleedingEdge\libmono\unityjit).
My question is: Are there any known disadvantages for this (for using the Mono library instead of System one)?
Thanks.
My target platform is Windows 64-bit only. Unity 2018.2.0f2 Scripting Runtime Version: .NET 4.x Equivalent Scripting Backend: Mono Api Compatibility Level: .NET 4.x