-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change SQL Server to SQLite #184
Comments
Originally it was all based on SQLite, we had so many threading issues that we decided to switch to something more reliable. Now that SQL Server is available for Linux and can be run in a container the issues seems less relevant. Thoughts? |
Hmm, we usually run integrated tests with SQLite and I don't remember threading issues to come up. May be these are already fixed? SQL Server container alone is several gigabytes. May be using a database abstraction and allow people using something like PostgreSQL? |
It's the first time this has been suggested, but I can sympathise with the reasoning. I suggest that we poll for opinion on the prerequisites in some of the upcoming workshops we have and then revisit this. |
I with great certainty can predict that this will be a demand very soon, as the .NET Core will spread and people will use more of containerised environments. PgSQL container is like 100Mb and SQL Server is a few gigabytes. |
As soon as the upcoming support for PostgreSQL in SQL Persistence is out, transitioning everything to PostgreSQL and containers is a feasible step. |
All excercises and the demo require SQL Server, which is problematic for people running macOS and Linux. I would suggest using SQLite since it will run everywhere.
The text was updated successfully, but these errors were encountered: