220 results found
-
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 -
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 -
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 -
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.
-
AUTO_INCREMENT
When I insert new record to table using table editor, ( id int(11) UNSIGNED NOT NULL AUTO_INCREMENT ) new field doesn't give the proper ID number. Seems like the editor can't find next free ID on auto increment field
1 vote -
1 vote
In case you were referring to Static Data in Script Folder, it’s supported
-
turn off data types in column headings
I dont need data types in column headings, it disturbs me.
3 votesAn option added.
-
utf8mb4 support
The databse charset set to "utf8mb4" and the collation set to "utf8mb4generalci". The table set as same as database, this field same as database. But when run query statement, all the chinese character was unreadable, the comment of field does too. For the comment of field, the correct string should be "地区Id", when I edit the table, he character look such as "鍦板尯Id". The other mysql studio works fine, such as MySql Workbench, Navicat.
1 vote -
bugfix
After a few hours open, either maximized or minimized, it gets frozen, I cannot click in any button. It is like if an invisible modal button is blocking the input. This is the latest version 7.3.131. please let me know how can I help you find the issue
1 vote -
17 votes
-
Error reports with no email client
Few people still use email clientes in their laptops these days. I frequently see errors in dbForge Studio, I frequently find errors on the new 7.3 version, but I cannot send them.
It's 2018, please create an API to receive these errors without requiring email clients.
1 vote -
Save current session before close the application
Save opened windows before close the application
3 votesThis can be achieved with the Database Project feature. You can add the necessary documents in the project, save it and select ‘Load Last Opened Project’ under ‘Environment Settings’ in the ‘Environment → General’ branch of the ‘Options’ window. So, next time you open dbForge, your documents will be opened automatically.
Also, by default, the documents auto save feature is turned. Despite the fact that the documents may have not been saved yet, next time you start dbForge, all tabs will be restored. You can specify the file types to restore in the ‘Restorable file types’ section of the ‘Environment → Documents → Restore’ branch in the ‘Options’ widow. The restorable files with corresponding paths are specified in the *.xml file that is located in the following folder:
SystemDrive\Users\%UserName%\AppData\Roaming\Devart\dbForge Studio for MySQL\ -
Ability to give custom alias or nickname to query result tab
Add a setting to give a custom alias or nickname to the query result tab that appears when executing multiple queries within the same SQL script.
For example running 'F5' on the following queries:
SELECT * from addresses a;
SELECT * from buildings b;Will return two query result tabs named like so:
TABS: [addresses];[buildings]
(It seems dbForge names each resulting tab based on the primary name of the first table within each of the select statements)
41 votes -
Data editing Mode per Categories and/or Server
Set the Data editing Mode (RO o. RW o. Ask) per Categories.
Sample:
Live = RO
Defelopment = RW3 votesPlease note that there is a feature allowing to change a connection’s color:
1. Right-click a connection in Database Explorer and select ‘Modify Connection…’ from the popup menu. The ‘Database Connection Properties’ dialog opens.
2. In the ‘Document Category’ drop-down menu, select the appropriate item or add a new one by clicking the three dots button against the drop-down menu. -
Script generation auto_increment bug
When backing up a database or creating CREATE script from a table, the auto_increment attribute is not set on a column which is not defined as a primary key.
eg.
CREATE TABLE wpquestionsformelement (
elementid int(11) NOT NULL AUTOINCREMENT,
formid int(11) NOT NULL,
elementorder int(11) NOT NULL,
elementtypecode varchar(50) NOT NULL,
elementparams varchar(3000) DEFAULT NULL,
questionid int(11) DEFAULT NULL,
attachmentid int(11) DEFAULT NULL,
mandatory bit(1) NOT NULL DEFAULT b'0',
deletedflag tinyint(1) NOT NULL DEFAULT 0,
PRIMARY KEY (formid, elementorder),
INDEX idxwpquestionsformelementelementid (elementid)
)
ENGINE =…1 vote
- Don't see your idea?