|
Hey Jörg!
These are all great requests. Please do create
Bugzilla entries for them and we can look at them for improvement in
Galileo!
Thanks!
--Fitz
Here's
another few:
- There should be a button for "Execute SQL" or similar within the SQL
editor tabs
- Support for explicit configuration of auto-commit is missing; it's not
clear what the default is here, are connections auto-committing or not?
- "Commit" and "Rollback" buttons inside the SQL editor tabs would be good
- A keyboard shortcut of "Ctrl+Return" for executing SQL would be what
probably a good number of people are trying out to execute their SQL...
- In the SQL results view, being able to right-click and "Copy to
clipboard" on individual cells would be very nice
Shall I open
some enhancement requests in Bugzilla?
Regards,
Jörg
Jörg von
Frantzius wrote:
Hi,
it took me quite a while to find out that DTP is
actually useable for me, but only after reading this newsgroup and fiddling
considerably.
I'd have two remarks for the moment:
- Creating an "SQL scrapbook" should be accessible from the "File" /
"New..." menu, just as is "SQL file" at the moment
- Creating an "SQL scrapbook" should be accessible from the context menu
of a database, auto-connecting it if chosen
- Why is there a differentiation between "Max row count" and "Max
display row count", i.e. why should "Max row count" be retrieved if only
"Max display row count" rows are shown? When I started off with the
defaults, I issued a query against a large table which never seemed to
return, since all rows were fetched. That made me think yesterday that DTP
is totally unusable. At least the defaults should be reasonable here, e.g.
50 and 50.
These issues currently make it hard for anybody
unfamiliar with DTP to get going quickly and having a good impression while
doing so...
Thanks in advance in case these issues would be looked at
:-)
Regards,
Jörg
|