Development discussion for DB Browser for SQLite (previously SQLite Browser)
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"? Both actions are so frequent here for me and I'm afraid my mouse suffers a lot as I click it so often on these buttons. Also, and this is no less important, it must confirm the deletion as this is a destructive action. And we don't have Ctrl-Z at all.
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...
OK, being a programmer too I see it's not an easy take to implement undo-redo functionality. Still, it's easy to add defensive confirmation OK/Cancel window before you actually delete a record. Will submit this request at Github along with keyboard navigation shortcuts.
Thanks!
I know this behaviour and it suits well when filling one simple table down the line. My scenario though is different. I learn Greek now (my native is Russian), and as part of this effort I develop and maintain my own dictionary. It consists of many tables which are dependant one on another. Say, nouns have their own table which has links to various reference tables (type, gender, number, declension etc.), then every noun has 1+ translations, then every translation has 0+ usage examples, 0+ references into our paper textbook, etc. Another table bears links between words, like, "this one derives from that one", "to better understand this word, also look up that one", and so on; they're all foreign keys obviously. So, to enter another noun into my dictionary, I need to insert records into several tables in particular order. So I constantly switch between tables. This makes DB4S loose focus: after changing table, the focus is always on the first row; but I can use Ctrl-End to jump there, and Tab to start a new one.
Still, this Tab-based navigation doesn't work for tables which have some NOT NULL columns; you can only INSERT into it by calling Add New Record popup which you can only get by clicking corresponding icon on the toolbar.
It would be just great to have a shortcut for that "New Record" button, with the same behaviour: Grid input for simple tables, and popup window input for anything more complex (plus to be able to reach Value column with Tab key).
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+ :-( ...
We've started putting together the pieces for a 3.12.1 release, and at first glance this seems like a simple enough change that it could be included. :)
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.Can't really claim good support for markdown (with any honesty) any more. :wink:
Story translation is different than software translation
There has already been a mention of this on our wiki.
However, I can not say that I am not responsible by just for mentioning on the wiki. I really sorry about this.
From next time, I will try to make it clear inform to the translators.
Maybe I can add comments in all shortcut entry(When do like this, Translators can check it in Qt Linguist).
Thank you for always taking the time to contribute to the our project.
That wasn't what I mean
What I mean is that dont workaround problems that can be simply fixed by informing.
I know a lot of "translators" that would come and ask you that HTML and placeholders are not of thier business.
We can't remove such stuff.
That's what I meant
You don't need to be sorry. My idea is to make translators cope with the tech behind software translation.
eg "Hey, could you do XYZ next time around, instead of ABC?"
@SafaAlfulaij I'm really sorry for the inconvenience and not understanding you.
The reason I didn't understand properly was because my native language wasn't English, so I lacked a lot.
Also, as @justinclift said, I have been involved in this project lately, so I'm still trying to learn and get used to the project.
Of course, I'm not trying to evade responsibility and no an excuse too, I am asking for understanding.
I will try to find out what you said and do not cause any inconvenience to the contributors. I apologize again. (Also, thank you for always paying attention to our project.)
