3 ms·
Ah! I figured it out. User error. I had hit "open file" instead of "open database" and the application decided to open the 30mb sqlite DB as text (e.g. a sql qu
by numlocked 2y ago
Ah! I figured it out. User error. I had hit "open file" instead of "open database" and the application decided to open the 30mb sqlite DB as text (e.g. a sql query), including syntax highlighting. Simply letting it grind away for 10 minutes or so allowed it actually open the file, at which point I could close the tab and performance is back to normal. Look forward to experimenting!
- jchw 2y agoHey, that's some amazing QA work. If I were the developer, I'd add a quick check to see if the file appears to be a SQLite database and do something useful in that case.
- semi 2y agoProbably good to have some basic checks too if it's expecting a text file of SQL queries- like a dismissible warning if it's over a certain size or doesn't appear to be plain text
- RyanHamilton 2y agoThanks for letting me know and great QA. Another user reported this just last week and I hopefully have it fixed: https://github.com/timeseries/qstudio/issues/49 https://github.com/timeseries/qstudio/issues/49 qStudio 3.04+ now only opens .sqlite/.db/.parquet as data files not for text editing.