-
Notifications
You must be signed in to change notification settings - Fork 137
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
Consider using SQLite for the database #15
Comments
I was initially thinking about this, but AFAICR there are some MS SQL specific items, that I did not know how to replicate. |
Thanks for the suggestion. What do you guys think? |
I am not an expert in either SQLLite or MS SQL server so I'm using this as a learning experience. What I do know is that a corporation is likely to be very hesitatnt to hook up a random project to their database server without thorough vetting. Another point is removing the requirement to install a SQL Server will make it much easier for new people to engage with the project. |
Yes, I agree that MS SQL will be a high friction point. Having all that, users can choose any db engine |
Is there any decision about db interface? EF core seems to be a suitable framework. |
yes, this has changed. This will allow us to take out any dependency on databases in the main project. |
So, are all dataretrivers will be realized as plugins? And what about strategy interface? Especially external strategies written with python or c for example. |
+1. It would be great if this can integrate with other language than C# |
YES The strategy interface will be also designed as a plugin, but this time as a UI plugin. I need to think about how exactly. I'm open to new ideas :) |
I have an idea of a strategy as a blackbox, which receives configuration then gets market data and sends signals (buy, sell, hold, etc.) |
I'm closing this, since we are not dependent on DB any more. |
SQLLite would allow the database to be stored as a local file and not require installation of any SQL server programs. More investigation required.
The text was updated successfully, but these errors were encountered: