466 results found
-
Routine code gets whipped out when a parameter added
If you editing a code of a routine (procedure or a function) but has not compiled it yet and then you add a parameter, the code of the routine gets refreshed and you loose all the code code you wrote before latest compilation. There was no such an issue in older versions of dbForge for MySQL (tested on 10.1.24)
3 votes -
Source control lost SQL SECURITY options
When submitting routines to SVN through 'Source Control', the SQL Security option is lost
6 votes -
Allow Schema Comparison to ignore differences in integer "size"
In versions of MySQL prior to 8.0, integer values were specified with a "size", such as "INT(11)". In MySQL 8.0 and newer, the size property of integers is removed, resulting in the same value having the type "INT". This results in Schema Comparison across MySQL versions (5.7 vs 8.0) reporting false-positive differences for tables.
The "ignore data types" option in Schema Comparison does not resolve the false positives, and is also probably too blunt, because column size does matter for text and binary data. Please add an option to specifically ignore differences in the "size" of integers.
1 vote -
Support displaying multiple databases in a connection
Currently, in Database Connections Properties, you can only select a single database or check the Show all databases checkbox. It would be useful to be able to select multiple databases in the dropdown. As an example, we could then select informationschema, mysql, performanceschema, and sys and put them under a MySQL connection.
1 vote -
Update Schema Comparison to improve cross-version comparision of Views
When comparing Views between MySQL 5.7 and 8.0, Schema Comparison detects "differences" to two conditions that are actually equivalent, resulting in false-positive change detection.
- Quoted text strings are prefixed with _UTF8 in MySQL 5.7 and _UTF8MB3 in MySQL 8.0. These are actually the same character set and represent no change. In fact, if MySQL 8.0 reported UTF8, it would be different, because in MySQL 8.0 the meaning of UTF8 is now UTF8MB4.
- In MySQL 8.0 Views, the schema prefix on table names (schema.table) is automatically removed when the schema of the specified Table matches the schema of the View. Therefore,…
1 vote -
Fix Schema Comparison issue for Stored Functions that return text values
When comparing Stored Functions that return text values using Schema Comparison, it should display the correct character set and collation as reported by information_schema.routines.
Currently, when comparing a MySQL 5.7 source host to a MySQL 8.0 replica of that source, Schema Comparison incorrectly reports the character set and collation of the RETURN value of Stored Functions that return text values on the MySQL 8.0 host. This leads to false positives in the reported list of schema differences.
For example, actual RETURNS value:
RETURNS VARCHAR(80) CHARSET utf8mb3 COLLATE utf8mb3generalciReported RETURNS value (incorrect):
RETURNS VARCHAR(80) CHARSET utf8mb4 COLLATE utf8mb4…2 votes -
Add option to remove database name from tabs
Currently all tabs look like <dababasename> .<objectname>. I normally have tens of tabs opened which takes too much of space but more importantly I can NOT see the object name as it gets shortened. Could I have an option to show tabs without the database name. Such a feature exists in SSMS
2 votes -
SQL notebook that can be global or per database. This can be helpful for storing and retrieving reusable SQL queries without saving files
SQL notebook that can be global or per database. This can be helpful for storing and retrieving reusable SQL queries without having to save and organize a bunch of .sql files in folders somewhere.
This is especially useful for complex queries for specific DBs or global generic ones. Also for sharing with a team.
Key word searching or tags would be nice as an option in it too1 vote -
Add an option to set default data formats used when 'Copy Data As'
Currently the data format for some field types like date, datetime, time, etc, has a default formatting which is not modifiable when using 'Copy Data As' feature, it changes to a format that isn't working for me now, so it will be nice to set default formats by the user
4 votes -
add the ability to change individual table color in the database diagrams
allow the user to specify the header color for a table in a database diagram. ideally you would optionally be able to make it 'sticky' and affect the table in all diagrams
3 votes -
horizontal toolbars
I see now a vertical tab instead of a horizontal tab as usual. I cannot figure out how to reset the app to its normal behavior. Also how do I enlarge the font of the stored procedures and table editor, it's too small for my old eyes.
1 vote -
copy and paste
copy anda paste from view data and excel not work
1 vote -
select, copy and paste objects between diagrams
allow objects to be 'copied' between diagrams. I would like to be able to select a group of tables from one diagram and create a new diagram from those selected tables.
1 vote -
github copilot
Are there any plans to introduce GitHub co-pilots into dbforge studio for MySQL?
7 votes -
bug in table edition with graphic table editor
the table designer has a BUG. A table column can have as a default value an internal server variable, in my case @@bindaddress. The correct way to add it (@@bindaddress), and it works. But when the table editor reverses a table definition, it misinterprets these defaults and saves it back wrong.
1 vote -
Delete multiple rows
Hello,
When deleting multiple rows, the application deletes them one at the time.
If you could use a "IN" condition with the primary key, if any, the execution will be must more faster.1 vote -
Better error message in data comparison (table name)
Hello,
When doing a data comparison and having an error, a message such as the following one is displayed:
"Error (1,1): Duplicate entry 'WBAH2022-2' for key 'Old'"The problem is that, when the data comparison is against tables, it's not easy to find the table with the problem. It would be very useful to have, at least, the name of the table.
Having also the value of the primary key would help further for this kind of error.
3 votes -
Allow variable identifiers to be user defined to accommodate multiple environments.
We are unable to define delimiters for variables. This causes query code from dbForge to fail when copied to a java based production environment.
Currently the dbForge variable delimiters are not compatible with many environments.
Provide means for users to define variable delimiters like DbVisualizer does.
2 votes -
Add option to disable autocommit
PLEASE add an option to disable autocommit at the connection level. It should be in the connection parameters so that it is switched OFF when you open the connection, and remains OFF unless you specifically enable it in a transaction. This seems like basic, common sense. autocommit is EXTREMELY dangerous when working in a production environment. It is unacceptable that there is no ability to control this basic feature at the client side.
3 votes -
"Modify via SQL" always Refresh automatically before opening Editor
When we work in Stored Procedures we already overwrote accidentially code as we were working in different windows and worked on an old version of the code
It is annoying to always need to refresh first to make sure that no old copy of the code is edited.
3 votes
- Don't see your idea?