Development discussion for DB Browser for SQLite (previously SQLite Browser)
plugins/imageformats/qsvg.dll
from the DB4S install directory. Our Qt dll's at the moment are version 5.12.8. Instead of that qsvg.dll
being all that's needed, that dll turned out to have a dependency on Qt5Svgd.dll
(which we weren't packaging).Qt5Svgd.dll
.Qt5Svgd.dll
from that was being picked up and loaded.Qt5Svgd.dll
with our packaging, so there's no need for the OS (or whatever) to go looking around for a potentially different one.
Hi Martin, thanks for answering me so soon. I know, that's true (the fact that surroundings field chars are not always a must), but I think a "compelled" surrounding char (for alphanumeric or all fields) could be a good idea.
Excel is not so smart in "understanding" CSV files (and it likes semicolon instead of comma... ;-) ).
As far as I remember though, (have to check on csv-spec.org) if a field is full of spaces and is text, it could be very likely be surrounded by single quote, double quote or other char. This is NOT a must, but not al CSV parsers are as good as the CALC (by libreoffice) one, and some of them fail if not well syntactically instructed ;-).
Anyway SqliteBrowser is a very good piece of sw... although the "Browser" part of the name, is a bit reductive: it is much much more than a simple browser!
Luca
latest Sqlite db version and all data types in it
Data types in sqlite hasn't changed. https://www.sqlite.org/datatype3.html
Its still nulls, integers, reals, text and blobs.
Can we have keyboard shortcuts for "Insert a new record" and "Delete the current record"?
Ideally, these requests should be requested on the github page (https://github.com/sqlitebrowser/sqlitebrowser/issues) as they're then logged, and the code is linked to the issue. You'll also be notified when the request has been added.
And we don't have Ctrl-Z at all
You do have a 'revert changes' button... ;)
When in "Add New Record" Dialog, I can navigate, by means of keyboard, through its elements BUT cannot reach that "Value" column
Can you not use the grid for entering data? A new record adds an empty row at the bottom of the grid, and you can enter your data ala Excel.
@chrisjlocke Thanks for the replies!
I will submit that new shortcuts request to Github, sure.
You do have a 'revert changes' button... ;)
"Revert Changes" drops everything since last save, it cannot correct my last action only… Imagine I input 10 records right and then did a mistake at the 11th—I cannot drop it all.
Can you not use the grid for entering data?
Grid only appears when a table is simple enough? For example, one of my tables has ~10 columns, some of them being mandatory, and no matter if I choose "New Record" or "Insert Values…" option I get modal Add New Record window where I can't navigate to the Value column easily.
Yes, if you have some fields (I believe) set to 'Not Null', then an empty row can't be inserted, so the dialog pops up.
Undo...
I think there were discussions about using savepoints, but the database isn't committed until the last savepoint is committed, so if there was a series of savepoints, at every insert/delete for example, you could undo going backwards, but would need to hit 'Save' to commit which would kill all the undos. You just know someone is going to hit Save /then/ want to undo...
Oh I forgot to highlight a little problem with long "headers". My genetic file has 19 comment # lines, then there is the header at line 21 and from 22 start the datas. In this situation I had to cut away manually first 20 lines (with sed) in order to be able to import them to sqlitedbbrowser. It would be nice to be able to jump some lines of the useless comments header. I'll prepare an example to show the problem.
Here is the example I described some msg before:
http://thinkitbetter.com/store/dl/Annot-SAMPLE.zip
It is a genetic hugely modified and cut of only 10K lines instead of 850K. I was able to load it in sqlitedbbrowser only after having deleted first 20 lines manually from a text file of 1GB+ :-( ...
QMake as the build system used in Qt 5 has lots of quirks and limitations. For Qt 6, we aim to use CMake as a standard 3rd party build system to build Qt itself. CMake is by far the most widely used build system in the C++ world, and better integration with it is sorely needed. We will continue to support our users on QMake, but not develop it further or use it to build the Qt framework itself.