7 results found
-
Source control lost SQL SECURITY options
When submitting routines to SVN through 'Source Control', the SQL Security option is lost
6 votes -
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 -
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 -
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 -
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 -
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 -
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
- Don't see your idea?