Carlo Sirna

opps... I noticed right now that this pull request contains also the changes I made for my other pull request... Sorry I am not very experienced with git, I am...

My pull request (https://github.com/thecoderok/Unidecode.NET/pull/16) now contains also a fix for this memory usage problem. this issue has been mentioned also here: https://github.com/dotnet/runtime/issues/54688 reading that thread I learned that the problem...

Because SqliteAsyncConnection is not really a connection: it is a **global static dictionary** of regular SqliteConnection instances that get shared among all possible threads and tasks in your application. oversimplifying...

what do you mean?

There is one thing I do not understand in your proposal: all these functions - QueryScalars(string sql,...) - Query(string sql,...) - Query(TableMapping map, string sql,...) **make absolutely no use of...

In my example Sqlite does not try to do anything regarding the table name: there isn't any table in the example database. sqlite-net needs to know the phisical table name...

the checks fail because of this error: "Testhost process for source(s) '/Users/runner/work/sqlite-net/sqlite-net/tests/SQLite.Tests/bin/Debug/netcoreapp3.1/SQLite.Tests.dll' exited with error: You must install or update .NET to run this application." I don't understand why, with...

But... is now sqlite-net a dead project?

PS: I already implemented this stuff and I am using it in a production environment. I use it in a "search dialog" where the user sees the records matching the...

the "regular" sqlite-net dll does NOT support encryption. you need to use a customized sqlite implementation (named sqlcipher) being developed by zetetic https://www.zetetic.net/sqlcipher/ I use it in an android project....