468 results found
-
Allow disabling quotes for SHOW CREATE TABLE during schema compare.
Give an option to run SET sqlquoteshow_create=OFF; before a schema compare. So that the schema generated via MySql does not add the quotes to everything.
6 votes -
allow schema-level environment category labelling
In the Database Connection Properties dialog, you can set the Environment Category to Production/Test/etc.
I have multiple instances where one database server holds the Test and Production schemas. It'd be nice to be able to label each schema accordingly.
6 votes -
Create new, delete old, rename... when rebuilding indexes
When a index has been modified that causes the index to be rebuilt, add a option to rebuild using the following flow.
Create new index with temp name.
Drop existing index.
Rename index with temp name to correct name.For tables that take a few hours to build indexes on, this will allow the existing index to remain being used while the new one is building. Then once it is built, remove the original index.
6 votes -
Change color of tab and status bar to match connection
It would be really useful to use more color to highlight the current connection in the active window, e.g. ability set tab and status bar background to red to match the color attribute of the connection
6 votes -
Refactoring does NOT take care of procudures and views
This is a big problem for me.
I renamed one table using the refactoring function.
But all views and procedures which used this table were not automatically changed as I expected.
Now I can't even open the views or procedures to manually edit them. All I get is: "unable to parse source text" which derives (so I think) from the now no more existing tables.
I was able to edit the views with the help of phpMyAdmin. But I can't edit the procedure.
This is a big issue for me.5 votes
AdminDevart
(_, Devart)
responded
Could you please describe the steps to reproduce the issue in details?
Please also provide us the CREATE definitions of the objects.
Additionally, please specify the version of dbForge.
-
data comparisons, add abilty to view by row stacking
While viewing records in data comparisons, add abilty to view in column side-by-side (as currently available) -OR- by row stacking
5 votes -
Comma separated values when copying cell data
When you copy cell data, for example 5 ids, I would like to be able to copy them as comma separated data in order to use in IN statements.
For example, if you have 3 rows of results like the following:
id name
1 George
2 John
3 GregoryI wish to copy ids as comma separated values in order to use them in a Select statement like:
SELECT * FROM temp t where t.id in (1, 2,3)5 votes -
5 votes
-
SQL History: log in plain mode without parameter
I know that in SQL LOG dbforge could store ALL query sent to DB. It would be great if dbforge stored them in plain form with parameter already substituted (not with :p1, :p2 .. and so on)
5 votes -
Show/Hide additional document views
With new DBForge update (2020), keyboard shortcut to show/hide additional document views is gone. Please add this feature back as it was extremely convenient to show/hide data results when writing long procedures.
5 votes -
Duplicate Current Code line
This is a proposed SQL Document shortcut key. When working in Text view, there is a shortcut using Ctrl + L:
Delete current code line and copy it to clipboard
I propose a similar shorcut using Crtl + D:
Duplicate current code line
This will make a copy of the current line right below it. This is especially useful when creating new queries based on the current one that may only require slight modification to the parameters.
5 votes -
SDE Full Document Recovery Options - when dbForge app crashes
This is marketed as an enterprise-grade dev tool. After years of use I was astounded to discover dbForge doesn't have decent full document recovery when the app crashes. The app doesn't crash much so it is a shock when it does, and then takes your unsaved SQL development code with it.
Every editor should be auto recoverable upon reload - SQL editor, Query editor, Stored Proc editor. All open windows in dbForge should be offered for recovery upon relaunch.
5 votes -
Ability to Compare All Schemas in a Connection
Rather than 1 schema at a time, allow to compare schema/data on a per connection basis, with an include/exclude schema list. For those of use with multiple schema's to compare this would be great!
4 votes -
Better error description when concurrency exception occurs
I opened a table and focused some data row. Then I created a new sql and did a few queries, one of them deleted a row in the table I've previously opened. But I didn't notice it. Then I returned to the opened table and edited the focused row (the one that was already deleted actually) and I got very generic error message, something like "An error has occurred during update operation". I spent a minute to understand that this is a concurrency exception because I've deleted a row I wanted to edit.
4 votes -
Warn about the use of @ in Stored proc parameter names
I used @ in a SP parameter name and spent some time trying to figure out why my procedure didn't work.
Turned out you can't? use the @ character in the name.
In the SP builder it might be handy to restrict invalid characters in param names.
4 votes -
4 votes
-
Naming Convention
It would be great, if I can set a naming convention.
Foreign Keys, Primary Keys, Table and Column name4 votes -
DB Health Analyzer
Implement MySQL server health monitoring tool that can visualize server workload, memory consumption, IO operations, etc.
4 votes -
Validation of variables in procedures
Additional validation when saving a procedure to check that all variables used exist either as parameters or variables would be very handy.
4 votes -
Generate cleaner SQL
It would be really nice if dbForgeStudio generated cleaner SQL code. Currently, the code generated by dbForge is very confusing and differs too much from the code generated by hand. There is no option to turn some settings off.
This is a problem if we need to maintain SQL scripts that are manually edited later. Everytime we need to export a script, we need to manually format the code and remove all the unecessary stuff.
Some of the issues are:
1) Every identifier is escaped even if it is plain english text. View generation gets really confusing by escaping every…
4 votes
- Don't see your idea?