search

PardeeCenterDU / IFs-Issues-Tracking

This repository only holds the list of bugs that have been reported for IFs. Anyone may add a bug report, but please look to see if your issue has already been added!
2 stars 0 forks source link

Opening IFsHistSeries.db in sqlite studio #302

Open mtirfan66 opened 2 months ago

mtirfan66 commented 2 months ago

As some of you know, it takes quite a bit of time each time to open IFsHisteries database in sqlitestudio by double clicking on the .db file. I need to look at the data frequently though, by opening the file in the studio and opening the tables that I need to look into.
Is there something I can do to accelerate the loading of it in the sqlitestudio? Is it possible to load it once and access it later without having to reload even though the sqlitestudio (and, the device) is closed/shutdown in between? Thanks, in advance.

PardeeCenterIFs commented 2 months ago

Yutang recommended we try DBeaver for the same reason, and I think is much faster.

https://dbeaver.io/

You can even leave your connection open between sessions and the file will be already open next time you reopen DBeaver.

mtirfan66 commented 2 months ago

That's great, Yutang. I would look at that. I would like to use one tool though, as much as possible. By the way, I started an incident in the sqlitestudio issue tracking and they got back to me. They wants me to share the database or an empty version of it - they think it's the schema that has a problem. Here is the response - "It may be hard to reproduce your specific conditions. Do you think you could share the database file with me privately (no need to make it public)? You could delete all data from tables. I'm interested mostly in the schema of the database."

I guess we have no problem sharing the entire database (.db). I can put it on a google folder.

mtirfan66 commented 1 month ago

Sqlitestudio developers marked it as a bug to fix in their next release (3.4.5)