4 ms·

How does this compare with https://sqlitebrowser.org/ https://sqlitebrowser.org/ ?

• jksmith 2y ago
  My goto as well.
• knighthack 2y ago
  That's my Swiss knife. Super handy in a lot of scenarios, and I use it side-by-side with Jetbrains' DataGrip.
• hochmartinez 2y ago
  I've used both. Sqlitestudio is far more powerful, intuitive and easy to use. Fast and efficient. Flies even in old PCs. In Linux you won't find It in the repositories. You have to download and run a handy installer.
  • Jach 2y ago
    It's in gentoo's default portage tree
  • 0points 2y ago
    It's in AUR
  • dotancohen 2y ago
    It's GPL, so why no Debian packaging, if it is popular?
    • shortrounddev2 2y ago
      Anecdotally, but I see less and less software distributed through apt these days
    • mappu 2y ago
      The ITP was in 2016, but it seems like it didn't really progress from there - https://bugs.debian.org/827236 https://bugs.debian.org/827236
  • pmarreck 2y ago
    FYI to anyone on Nix/NixOS, sqlitestudio is available on unstable branch of nixpkgs: https://search.nixos.org/packages?channel=unstable&show=sqlitestudio&from=0&size=50&sort=relevance&type=packages&query=sqlitestudio https://search.nixos.org/packages?channel=unstable&show=sqli...
• PeterStuer 2y ago
  I have been using sqlitebrowser as well. Fairly satisfied, except for the poor 'export to csv' that seems to fail on respecting csv separations in some cases. Does SQLiteStudio handle this correctly?
  • justinclift 2y ago
    Do you have the specifics of the failure cases? We (sqlitebrowser.org devs) tend to fix bugs like that when we have a reproducer.
    • PeterStuer 2y ago
      Thx for replying here. My issue had to do with exporting text fields that have multi-line content and then importing that data into Microsoft Excel. I have quickly looked more deeply into this as for now I used a workaround by exporting to JSON. Upon investigation it does not seem like sqlitebrowser is doing anything explicitly wrong. It quotes texts correctly when necessary, in my case specifically strings that contain 'LF', and does not do it when it is not needed. The fault lies with the Excel importer that in this case does not correctly derive that it should use QuoteStyle=QuoteStyle.Csv (it uses QuoteStyle=QuoteStyle.None even when you instructed it to base its derivation on the entire dataset. I do not know if any accommodations on the exporting application can (or should) be made to compensate for Excel's import heuristics failures. P.S. for those running into the same issue (there seem to be many and I have not seen a solution from a quick Goolge that worked), in Excel when doing the import from CSV, select "Transfrom Data", open up the "Advanced Query Editor" and in the first line you will see something like let Source = Csv.Document(File.Contents("the path to your CSV file"),[Delimiter="#(tab)", Columns=13, Encoding=65001, QuoteStyle=QuoteStyle.None]), ... Just replace the QuoteStyle.None with QuoteStyle.Csv and you should be good to go. My apologies to the sqlitebrowser devteam for my initial misconception.
      • justinclift 2y ago
        No worries at all. I kind of wonder if using LibreOffice for the initial import -> Save to (say) Excel format would work better, than opening that in Excel? ie might be easier for people who aren't comfortable changing the default settings in things