At present I have to press ENTER before I can TAB to the next column. > If I type VARCHAR into the Data Type column and then press TAB I'd expect it to jump to the Size column. Is it really so much harder to tab to the Size field and add the size there?
#Dbvisualizer cell form read only full
This is harder than it may seem, because the data type list is retrieved from the database (so we don't have full control over what's in it) and it is read-only, so you can't type "VARCHAR(255)" making it editable would likely cause other problems. This one is a duplicate issue I've mentioned before but I mention it again as I still find it gets me nearly every time.
> If I enter VARCHAR(255) as a data type, I'd expect it to parse it into the Data Type and Size columns, not generate an error message. I know I can use CTRL-I to add a new row but that's far less intuitive.ĮNTER is used for so many things in grid editing that it is hard to also bind it to "Insert New Row", but you can bind something like Ctrl-Enter to this operation in Tool Properties->Key Bindings. > If I press ENTER on the last column of the row, I'd expect to to make a new row, not jump back to the first column. live, test and development versions) or customise the SQL by hand before the table is created. The Execute button does what it says on the tin but it would be handy to have an "Export to SQL" button too so that I can create the same table on several databases (e.g. At the moment I have to select the blank schema and scroll down quite a way to find dbo. The default schema for my connection should be selected when the dialog is first opened. If I type VARCHAR into the Data Type column and then press TAB I'd expect it to jump to the Size column. If I enter VARCHAR(255) as a data type, I'd expect it to parse it into the Data Type and Size columns, not generate an error message. I know I can use CTRL-I to add a new row but that's far less intuitive. If I press ENTER on the last column of the row, I'd expect to to make a new row, not jump back to the first column.
That dialog could also do with being more keyboard-friendly.
0 kommentar(er)
