sqlite-net VS UniTask

A common misconception about SQLite-net library is that it can't handle Foreign Keys in a local SQLite database. Actually, they are supported! Maybe not in the way you'd expect it, but it works.

My project really benefits from AOT compilation, so it's quite important for me to find something that works. I don't need anything fancy, just something that can execute queries and that works with native AOT without making the executable huge. Any ideas? I've tried the EF sqlite provider but it makes the executable literally hundreds of megabytes after trimming. I've also tried sqlite-net, but I can't get it to work when AOT compiled.

I don't live in the Windows world, so I can't vouch for the usefulness of the following library, but I do want to mention it for the benefit of anyone looking. There is in fact a single-file .NET C# library that implements SQLite. It's MIT license.

SQLite with https://github.com/praeclarum/sqlite-net is a very good option. MS even references this particular package a lot in their official docs and tutorials on Xamarin/MAUI storage.

How are you all calling your SQLite db's? Which nuget? I've been using https://github.com/praeclarum/sqlite-net . I'm wondering if there are any better/worse packages? Performance wise, flexibility wise, etc. I've been using this package for two different projects for a few years, seems reliable enough - but sometimes I wonder if I could get better performance. Although... Probably not enough curiosity to rip everything out and start over.

UniTask plus sqlite plus https://github.com/praeclarum/sqlite-net are awesome.

The dead simple way. sqite-net-pcl

Hello! Is there a way to configure database creation like what EF Fluent API does? I have found this PR Add Fluent API (v2) by RoyGoode · Pull Request #727 · praeclarum/sqlite-net · GitHub but there is no update since 2018.

If you develop projects in Unity - i really recommend to see at UniTaks.

Give the UniTask library a look https://github.com/Cysharp/UniTask

What I would say, however, is that I much prefer async / await via UniTask over standard Coroutines!

Lastly I recommend using UniTask to better await an asset load, use it, and release it without clunky Coroutines. Happy to give examples of how to use UniTask to update this code.

If you absolutely must muck about with threads in Unity yourself (though I struggle to think of a reason why you'd need to for the example given) then Unity's Jobs system is probably the way to go - though in most cases you can likely achieve whatever it is you're trying to achieve using something like UniTask (my preference) which gives you much nicer async / await support.

Great comment. The Unity task library is UniTask.

There are a few problems. Firstly use UniTask for async related things in Unity. Provides much better async integration with Unity.

This is where UniTask comes in. If your project relies heavily on asynchronous code-- it sounds like it does -- you'll likely enjoy this package. It doesn't allocate, hooks into Unity's PlayerLoop for per-frame timing, and allows for return types. You can even await existing Coroutines.

UniTask is a popular async/await library that doesn't have this problem.