243 results found
-
Fix error
dbForge MySQL 10.1.158:
When a stored procedure is very large, the reference to the database's created functions is lost and an error occurs. I still think that the best version they have released, by far, is 9.0.567; it has the fewest errors and is much more stable than the subsequent versions. I'm sharing the error that appears:
=========================
Exception Information
Place: 2
ExceptionId: 9ac1d2da-2b6b-417c-ab02-5046d2ba261e
Message: Referencia a objeto no establecida como instancia de un objeto.
Source: Devart.DbForge.DbEditors
TargetSite: Void Brgc(Devart.ComponentModel.Runtime.Severity)
HelpLink:
Type: System.NullReferenceException
Stack:
en Devart.DbForge.DbObjects.DbObjectEditor.Brgc(Severity )
en Devart.DbForge.DbObjectDocument.qrJN()
en Devart.DbForge.DbObjectDocument.irJP()
en System.Windows.Forms.Timer.OnTick(EventArgs e)
en System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
en System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd,…1 vote -
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 -
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 -
copy and paste
copy anda paste from view data and excel not work
1 vote -
9.2.105 Bug -- Cannot connect (SSL) to AWS Aurora MySQL
Using identical configuration and credentials, v9.2.34 (and previous versions) connects to my AWS Aurora MySQL instance over SSL. However, the v9.2.105 update does NOT connect. It returns a dialog stating "SSL connection error (2026): The server hello message uses a protocol that was not recognized."
I tried many configurations, but none worked. Uninstalled and downgraded, worked on first try. Updated to latest and repeated test, same failure.
1 vote -
Separate DEFINER and SQL SECURITY in exclude backup options
It only makes sense to combine these two options when SQL SECURITY is set to DEFINER. In the other case (INVOKER) it will cause a problem if the DEFINER is specified when restoring the database to a different environment - user will not exist or will not have the right privileges. "Exclude DEFINER" and "Exclude SQL SECURITY" should be two separate options when backing up a database.
3 votes -
Add ability to compare stored procedures with formatting applied
Having the ability to compare formatted versions of stored procedures would allow to ignore stored procedures that are identical even if they are not formatted exactly the same.
The performance cost would be marginal compared to the usefulness of sorting out equivalent stored procedures.
When comparing code, what it does is what is important.
1 vote -
retreive data with sql
I want to retreive data with editable sql (select statement). It could be implemented now, but I want it in context menu.
1 vote -
Code for CREATE TABLE with MariaDb "system versioning" is not generated correctly.
On a table with system versioning, from context menu I select:
Generate script as > CREATE > To new SQL window.
And the output does not include SYSTEM VERSIONING data at all.
When I run SHOW CREATE TABLE tablename - I get correct information.The same with "Edit table"
(In general it would be nice to set, if "Generate script" uses dbForge engine, or from database "SHOW CREATE TABLE", because output sometimes is drastically different)2 votes -
Code for CREATE TABLE with MariaDb "system versioning" is not generated correctly.
On a table with system versioning, from context menu I select:
Generate script as > CREATE > To new SQL window.
And the output does not include SYSTEM VERSIONING data at all.
When I run SHOW CREATE TABLE tablename - I get correct information.The same with "Edit table"
(In general it would be nice to set, if "Generate script" uses dbForge engine, or from database "SHOW CREATE TABLE", because output sometimes is drastically different)0 votes -
mariadb support system versioned tables
Support system versioned table syntax and settings toggle for tables/columns in mariadb 10.3+
For example
SELECT * FROM mytable FOR SYSTEM_TIME ALL
is not detected as valid syntax, nor is it suggested for code completion
Also need to be able to turn on/off system versioning per column/table in edit table dialog.1 vote -
MariaDB Spider Engine Comment Field Get Trimmed in generated Script when modified
We would store the connection information in comment, there is no problem when we first create the table in SQL script, but once we want to modify and generate the script from dbForge Studio, comment field get trimmed and stored information is missing
1 vote -
copy databaes not works when we try copy from ndbd to innodb cluster
copy databaes not works when we try copy from ndbd to innodb cluster.
if exist options skip engine it will be works1 voteNow, there is an option to ignore an engine.
-
4K Screens, adaption
On 4 K monitors displayed letters appear very small, difficult to read and another slightly bigger problem is, that some notifications and input boxes overlap and hide themselves a bit, f.ex. in IMPORT DATA function.
I currently help myself with changes in screen resolution.1 voteMany bug fixes for 4k monitors are made.
-
dark mode
all my apps have a dark mode.. it hurts my eyes to use yours
1 vote -
Mysql database copy from innodb to ndbcluster is notpossible
Mysql database copy from innodb to ndbcluster is not possible becuase when we copy we can't chose without engine set. In result on cluster each database use same engine as source (not clustered)
1 voteAn option to ignore engines is added.
-
Adding or altering a virtual field is not possible.
i upgraded to mysql 5.7 because i want to profit from the virual field feature. dbforge studio for mysql does not yet implement an editor for formulas in virtual fields.
1 vote -
Support compund statements in MariaDB
In MariaDB (as of 10.1.1), compound statements are allowed outside of stored procedures - see https://mariadb.com/kb/en/library/using-compound-statements-outside-of-stored-programs/.
9 votes -
1 vote
In case you were referring to Static Data in Script Folder, it’s supported
-
enhancment copy mysql database feature
In the present solution, you can't copy databases from MySQL ndbcluster - cluster to standalone MySQL.
not work from cluster to normal server because when we copy
we cant unselect engine type (on normal server not exist ndbcluster engine )4 votesPlease note that you can uncheck the ‘Include Engine’ option.
- Don't see your idea?