75 results found

1. Can't follow Caret when input Chinese characters

   When using Chinese PinYin input(such as QQ pinyin input), the input box will keep at the left-top screen, don't follow my cursor position.

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Bugs  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Do not display Object Does Not Exist error when object exists

   Scenario

   DB user has SELECT privileges on mysql.proc.
   DB user has ALL PRIVILEGES on schemaA, and NO PRIVILEGES on schemaB.
   DB user is running dbForge for MySQL 8.0.40
   A Stored Procedure (spA) in schemaA calls a Stored Function in schema A (fnA).
   A Stored Procedure (spB) in schemaB calls the Stored Function in schema A (fnA).

   Therefore, in the Database Explorer tree view, schemaA is listed, schemaB is not.

   Action

   The user expands the list of Stored Functions in schema A, expands fn_A, and then expands the "Used By" list.

   Result

   dbForge pops up an error message stating: Object "schemaB.spB" does not exist.
   Neither schemaA.spA nor schemaB.spB are listed under "Used By".

   Expected Result

   No error message
   schemaA.spA and schemaB.spB listed under Used By
   schemaA.spA is editable
   schemaB.spB is read-only

   Analysis

   Because schemaB is not listed in the Database Explorer, dbForge seems to be unable to list its child objects under the Used By section. When this error happens, it also causes the Used By section to not list ANY objects, even those in schemaA.

   The existence of schemaB is revealed by the query to mysql.proc, so that should allow the Used By section to display schemaB.spB, even if the user cannot edit spB. This is desirable, because it informs the developer that something potentially needs to be refactored if changes are made to fn_A.

   Scenario

   DB user has SELECT privileges on mysql.proc.
   DB user has ALL PRIVILEGES on schemaA, and NO PRIVILEGES on schemaB.
   DB user is running dbForge for MySQL 8.0.40
   A Stored Procedure (spA) in schemaA calls a Stored Function in schema A (fnA).
   A Stored Procedure (spB) in schemaB calls the Stored Function in schema A (fnA).

   Therefore, in the Database Explorer tree view, schemaA is listed, schemaB is not.

   Action

   The user expands the list of Stored Functions in schema A, expands fn_A, and then expands the "Used By" list.

   … more
   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminDevart (_, Devart) responded

   Could you please provide us the result of the following query:
   SHOW GRANTS FOR ’DB_user_name’@’host_name’

   You can send a reply straight to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .

3. BUG: When Copy & Paste As New Record string values are cut off after NON-Iso characters. Just like ä ö ü. even if it is defined as UTF-8

   BUG: When Copy & Paste As New Record string values are cut off after NON-Iso characters. Just like ä ö ü. even if it is defined as UTF-8

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Fix start of comment detection at beginning of line

   When editing SQL code in dbForge for MySQL 7.3.137, there is a case where it fails to detect the "start of comment" delimiter, and incorrectly intreprets the remaining text on the line as SQL code. This breaks the syntax highlighter, auto-complete, and ability to save stored procedures, functions, etc.

   Specifically, when using a double-dash "--" to start a comment in MySQL, it normally requires whitespace after the double-dash to be interpreted as a start of comment delimiter. However, when the double dash is at the beginning of a line, it does not require whitespace.

   See: https://dev.mysql.com/doc/refman/5.7/en/ansi-diff-comments.html

   Example:

   -- This is a valid comment
   --This is also a valid comment

   When editing SQL code in dbForge for MySQL 7.3.137, there is a case where it fails to detect the "start of comment" delimiter, and incorrectly intreprets the remaining text on the line as SQL code. This breaks the syntax highlighter, auto-complete, and ability to save stored procedures, functions, etc.

   Specifically, when using a double-dash "--" to start a comment in MySQL, it normally requires whitespace after the double-dash to be interpreted as a start of comment delimiter. However, when the double dash is at the beginning of a line, it does not require whitespace.

   See: https://dev.mysql.com/doc/refman/5.7/en/ansi-diff-comments.html

   Example:

   -- This is… more

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Be able to close connection from the stored procedure editor

   Not sure if it needs to be classified as a bug or a new features BUT!!!!
   I noticed today after our Aurora AWS Cluster failed over that I was not able to recompile a stored procedure I was altering.
   From a query window you can close the connection and an execute will open it again.
   But you can't close the connection from the editor!!
   And it's the same with Table Editor.
   I know you can close it from the DB Explore but it's inconsistent with the SQL Editor UI. You should have the same buttons.

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Bugs  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Support reserved keywords and events in MySQL 8.0

   dbForge Studio 2019 for MySQL 8.1.22
   When sync data between MySQL 5.7.25 and MySQL 8.0.15 and table have field name in reserver keywords, got error like "check syntax ", rank,", fields and tables names must be enclosed in apostrophes.
   MySQL 8.0 event like
   CREATE
   DEFINER = 'username'@'localhost'
   EVENT odatabase.eventname
   ON SCHEDULE EVERY '1' WEEK
   ...
   in GUI shows as "every '7' (SEVEN) weeks", but DDL is right.

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. output window

   1) meanwhile the execution of SQL script file if I click on some other window, ant then return in output window...the output windows shows the first output...and not the (more usefull) last one.

   2) please fix it! I have more than one schema. I select the first one. Open a SQL file...launch it. Ok. I open a second SQL file...THE SCHEMA CHANGE without show me the change and dbForge run the SQL script on the second schema!!! Damn it!

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Please save the current setting "Current Document" on the Find Dialog

   Please save the current setting "Current Document" on the Find Dialog. It defaults to 'All Open Documents' which is very dangerous

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. it cannot be brought to the foreground

   the latest version 7.3.137 once minimized or hiden by another program, after some time it cannot be brought to the foreground. And if you try to close it from the task bar, pops up a box to save any unsaved objects, but there is way to click on the buttons, it like something else is grabbing the input. In that state I saves a process dump. Please let me know how can I uploaded it to you.

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminDevart (_, Devart) responded

   You could upload the file to our FTP server ftp://ftp.devart.com@anonymous or any other place and provide us the link to download it.

10. The wildcard characters “%” and “_” can be used in the Host and Db columns of either table. These have the same meaning as for pattern-match

    Granting privileges has issues if the database name contains an underscore.

    If the database privileges have been defined on the mysql command line or in pma myadmin the underscores are escaped so that an exact match of the database name applies.

    eg.

    GRANT select on my\_db.* TO 'user'@'host'

    DbForge does not escape the _ character and creates a new privilege:

    GRANT INSERT on my_db.* TO 'user'@'host'

    If the 'my_db' escaped SELECT privilege is present then the INSERT privilege created by dbForge is ignored.

    The underscores in database and host names should be escaped out by dbForge when it genereates GRANT and REVOKE statements.

    See below:

    The wildcard characters “%” and “” can be used in the Host and Db columns of either table. These have the same meaning as for pattern-matching operations performed with the LIKE operator. If you want to use either character literally when granting privileges, you must escape it with a backslash. For example, to include the underscore character (“”) as part of a database name, specify it as “_” in the GRANT statement.

    Granting privileges has issues if the database name contains an underscore.

    If the database privileges have been defined on the mysql command line or in pma myadmin the underscores are escaped so that an exact match of the database name applies.

    eg.

    GRANT select on my\_db.* TO 'user'@'host'

    DbForge does not escape the _ character and creates a new privilege:

    GRANT INSERT on my_db.* TO 'user'@'host'

    If the 'my_db' escaped SELECT privilege is present then the INSERT privilege created by dbForge is ignored.

    The underscores in database and host names should be escaped out by dbForge when it… more

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. There's no effect in the setting of Hightlight SELECT Statement?

    I remember this effect is good for the text editor of the SQL,but why is no effect now?

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    AdminDevart (_, Devart) responded

    Could you please provide us a screenshot explaining this and describe the steps to reproduce the issue in detail?

    You can send a reply straight to our support system at supportATdevartDOTcom and alexaATdevartDOTcom

12. scroll 'wheels' do not work

    Whether used on my laptop with a touchpad or my desktop with a mouse, dbForge Studio doesn't support scrolling in any window by any means other than clicking or dragging the scroll bar. It will initially scroll for perhaps a second and then it stops.

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Bugs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    AdminDevart (_, Devart) responded

    You could try the following instructions http://www.microsoft.com/hardware/en-us/help/windows-8/how-to/mouse/use-partialscroll-mouse

13. Fix Stored Procedure Editor to accept ALTER TABLE xxx RENAME TO yyy

    As of dbForge for MySQL version 8.0.40, the Stored Procedure Editor (and Schema Compare) have started to throw errors when trying to open one of our stored procedures. I have traced it down to the presence of an ALTER TABLE command within the procedure.

    Here is a simple procedure that will trigger the error:

    DELIMITER $$

    DROP PROCEDURE IF EXISTS sp_test$$

    CREATE DEFINER=root@localhost PROCEDURE sp_test()
    MODIFIES SQL DATA
    BEGIN

    ALTER TABLE foo RENAME TO bar;

    END
    $$

    DELIMITER ;

    Specifically, if you try to open the procedure in the procedure editor, dbForge will display the error message "Unable to parse source text" and refuse to open.

    Similar error messages come up when trying to execute a schema comparison that includes affected procedure.s

    As of dbForge for MySQL version 8.0.40, the Stored Procedure Editor (and Schema Compare) have started to throw errors when trying to open one of our stored procedures. I have traced it down to the presence of an ALTER TABLE command within the procedure.

    Here is a simple procedure that will trigger the error:

    DELIMITER $$

    DROP PROCEDURE IF EXISTS sp_test$$

    CREATE DEFINER=root@localhost PROCEDURE sp_test()
    MODIFIES SQL DATA
    BEGIN

    ALTER TABLE foo RENAME TO bar;

    END
    $$

    DELIMITER ;

    Specifically, if you try to open the procedure in the procedure editor, dbForge will display the error… more

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Bugs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    AdminDevart (_, Devart) responded

    Could you please provide us the following information:
    1. Server version.
    2. Result of the following query:
    SHOW CREATE PROCEDURE sp_test;

    You can send a reply straight to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .

14. view with a UDF calling an aggregate function adds quotes around the aggregate

    I'm creating a view using the valid SQL:

    SELECT dateAsString(MAX(a.dateStart)) AS LastDate ...

    dateAsString is a UDF in my database that accepts a DATE parameter.

    The query executes fine. When I save it in a view, though, dbForge changes the query text to:

    dateAsString(MAX(a.dateStart))

    Which, obviously, won't work.

    Any thoughts?

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Bugs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    AdminDevart (_, Devart) responded

    Could you please provide us the following information:
    1. Version of the MySQL server.
    2. CREATE definition of the UDF.
    3. The assembly file containing the functions called by the UDF.

15. Find Invalide Objects

    == English ==
    The "Find Invalid Objects" wizard lists the following objects in the new version "dbForge Studio for MySQL 9.0.338":

    • Temporary tables are listed in Views as not being found
      In Vden Views, the temporary tables are e.g. created with the following command:
      WITH RECURSIVE TMP as Select .... from ...) Select ... from TMP

    • crdebug.ENTERMODULE2 is not found. It is searched in the respective database; but not in the cr_debug database.

    • crdebug.ENTERHANDLER is not found. It is searched in the respective database; but not in the cr_debug database.

    • No further objects from the crdebug database are found ... crdebug.UPDATEWATCH3, crdebug.TRACE, crdebug.LEAVEMODULE, crdebug.UPDATESYSTEM_CALLS

    == German ==
    Der "Find Invalid Objects" Assistent listet in der neuen Version "dbForge Studio for MySQL 9.0.338" folgende Objekte auf:

    • In Views werden temporäre Tabellen als nicht auffindbar gelistet
      In Vden Views werden die Temporären Tabellenz.B. mit dem folgendem Befehl erzeugt:
      WITH RECURSIVE TMP as Select .... from ...) Select ... from TMP

    • crdebug.ENTERMODULE2 wird nicht gefunden. Es wird in der jeweiligen Datenbank gesucht; jedoch nicht in der Datenbank cr_debug.

    • crdebug.ENTERHANDLER wird nicht gefunden. Es wird in der jeweiligen Datenbank gesucht; jedoch nicht in der Datenbank cr_debug.

    • weitere Objekte aus der crdebug Datenbank werden nicht gefunden... crdebug.UPDATEWATCH3, crdebug.TRACE, crdebug.LEAVEMODULE, crdebug.UPDATESYSTEM_CALLS

    == English ==
    The "Find Invalid Objects" wizard lists the following objects in the new version "dbForge Studio for MySQL 9.0.338":

    • Temporary tables are listed in Views as not being found
      In Vden Views, the temporary tables are e.g. created with the following command:
      WITH RECURSIVE TMP as Select .... from ...) Select ... from TMP

    • crdebug.ENTERMODULE2 is not found. It is searched in the respective database; but not in the cr_debug database.

    • crdebug.ENTERHANDLER is not found. It is searched in the respective database; but not in the cr_debug database.

    • No further objects from the cr… more

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating