04-17-2018, 10:58 AM
(This post was last modified: 04-17-2018, 11:04 AM by tommiehansen.)
(04-17-2018, 09:56 AM)askmike Wrote:Quote:1. Split the sets into actual files, this since SQLite db's can be finicky and prone to corruption. A single exchange/set corrupting is a zero-problem. An entire db with 10+ sets corruption less so. This would also make it around 5 billion times % easier to share sets, manage them, convert to other DB's ... etc etc ... etc.
A lot of people experience errors here, I had it happen only once before (around 2 years ago). What is your OS?
This is highly dependent on SQlite > Host OS (hence you ask). I haven't had much troubles myself but i know that file locking can be somewhat of an issue and can easily make a SQLite db become corrupted/malformed.
I have a lot of OS:es since i run Gekko on 6 computers. Some debian, some ubuntu, some win10 + wsl.
This topic was about solving the architecture of the dataset downloader though.
Another OS doesn't really have much to do with that?