240 results found
-
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.
-
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 -
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 -
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 -
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 -
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 -
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 -
Export data of the several tables at once
Data Export Wizard will allow to select multiple tables to export.
Database Explorer will allow quick export from several tables selected with Ctrl+Click.0 votesWill be included in the next release
-
Support access to MySQL servers on Amazon AWS
Ability to connect to MySQL servers hosted on Amazon cloud.
0 votesHello,
> Support access to MySQL servers on Amazon AWS
We would like to let you know that we have released dbForge Studio Beta for MySQL, v6.0 where the requested functionality is implemented: http://www.devart.com/dbforge/mysql/studio/download.html
Best regards,
Devart Team
http://www.devart.com -
on rightclick in editor - addt to menu - comment and uncomment selected lines
On rightclick in editor - add to menu new features - comment and uncomment selected lines (like in Visual Foxpro IDE)
0 votesThere is such a feature in dbForge Studio for MySQL. It can be accessed either from the ‘Standard’ toolbar or from the top menu by selecting ‘Edit→Advanced→Comment\Uncomment Selection’.
-
Enable Code Completion when writing stored procedure
There doesn't appear to be anyway to use code completion in version X when editing stored procedures? It works like a champ when writing a normal query
0 votesThis issue is fixed in the new build 6.0.151 of dbForge Studio for MySQL: http://www.devart.com/dbforge/mysql/studio/download.html
-
0 votes
-
Ability to rename file in project
Why can't I rename a file in a project? (I can understand why I can't rename files that are associated with database objects, but just a basic SQL script file?)
0 votes -
UI 'loses' SQL Security setting after schema compare
When we synchronise a DB schema with another we push the SQL SECURITY INVOKER setting but editing the destination/target procedure afterwards the GUI ignores this and reverts to DEFINER.
0 votes -
0 votes
-
replication
When you modify the database structure, e.g. delete a table in a particulary database, dbforge dont use that database, instead of that, modify directly the database information_shema, so there are problems in replication configurations.
0 votes -
Upgrade ssh connection / Can't connect on openssh > 7.0
OpenSSH 7.0 defaults to no support for diffie-hellman-group1-sha1 key
exchange.If we can't edit the config of openssh, we can't use the SSH security feature. Can you upgrade the lib and use one of the default protocol ?
0 votes -
0 votes
-
Fix false-positive syntax error detection when using UNION
I recently upgraded to dbForge 7.3 and discovered that the SQL syntax highlighter is incorrectly highlighting valid SQL (per MySQL 5.6) as if there is an error. Example SQL is below.
The effect is that the word "UNION" in the SELECT statement will display the red error underline (hover text: 'Identifier' expected) and the closing parenthesis will be similarly highlighted (hover text: Unexpected symbol ')'). If you run the query, the error highlighting will disappear until the SQL is edited, at which point it will immediately return.
-- SQL syntax highlighter bug in dbForge for MySQL 7.3.137
DROP TEMPORARY TABLE…
0 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
- Don't see your idea?