75 results found

1. You have a bug, this stored procedure has legal text, you can compile it, but it cannot be edited by the tool.

   You can compile this stored procedure but you cannot edit with your tool, it says that the code is wrong, but it is not.
   CREATE DEFINER = 'root'@'%'
   PROCEDURE simulation.comparebill()
   BEGIN
   with mybill AS(
   with billing AS(select c.day AS day,c.code AS code,cast(c.seconds as double) / 60.00 AS Mins,
   case when r.code is null then 0.005 when c.jurisdiction = 'Inter' THEN
   r.inter when c.jurisdiction = 'Intra' then r.intra else greatest(r.intra,r.inter) end AS rate,
   ifnull(r.description,'Missing Destinations at $0.005') AS description
   from (cdr c INNER join ratedeck r on(c.code = r.code))) select billing.day AS day,billing.description AS description,
   round(sum(billing.Mins),2) AS Minutes,
   round(sum(billing.Mins * billing.rate),2) AS Total
   from billing group by billing.day,billing.description WITH ROLLUP)
   select ifnull(mybill.day,'') AS DAY,ifnull(mybill.description,'') AS DESCRIPTION,
   lpad(format(mybill.Minutes,2,10),14,' ') AS Minutes,
   lpad(concat('US$ ',format(mybill.Total,2)),14,' ') AS Total FROM mybill
   WHERE description IS NOT NULL OR day is null
   ORDER BY day DESC;
   END

   You can compile this stored procedure but you cannot edit with your tool, it says that the code is wrong, but it is not.
   CREATE DEFINER = 'root'@'%'
   PROCEDURE simulation.comparebill()
   BEGIN
   with mybill AS(
   with billing AS(select c.day AS day,c.code AS code,cast(c.seconds as double) / 60.00 AS Mins,
   case when r.code is null then 0.005 when c.jurisdiction = 'Inter' THEN
   r.inter when c.jurisdiction = 'Intra' then r.intra else greatest(r.intra,r.inter) end AS rate,
   ifnull(r.description,'Missing Destinations at $0.005') AS description
   from (cdr c INNER join ratedeck r on(c.code = r.code))) select billing.day AS day,billing.description AS description,
   round(sum(billing.Mins),2) AS Minutes,
   round(sum(billing.Mins * billing.rate),2)… more

   1 vote

   Vote 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

2. 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 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

3. Optimize sequence for constraint alterations

   When you alter several constraints, drops come before adds.

   Where the changes are simple, it should be safe to group them in order to minimize the time that the constraint is not in effect. I have some huge tables. If I alter three constraints to switch from UPDATE to RESTRICT, for example, the third constraint is inactive until the table is literally copied three times.

   There's another post about grouping the alter commands together, and this would make a big improvement where each change causes a table copy.

   In the case I just ran into, however, the generated script was the least efficient method possible to make the necessary changes.

   When you alter several constraints, drops come before adds.

   Where the changes are simple, it should be safe to group them in order to minimize the time that the constraint is not in effect. I have some huge tables. If I alter three constraints to switch from UPDATE to RESTRICT, for example, the third constraint is inactive until the table is literally copied three times.

   There's another post about grouping the alter commands together, and this would make a big improvement where each change causes a table copy.

   In the case I just ran into, however, the generated script was… more

   1 vote

   Vote 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

4. Be able to disable GroupDatabasePrivileges query from executing in Schema Compare and actually NOT RUN the query

   Be able to disable GroupDatabasePrivileges query from executing in Schema Compare and actually NOT RUN the query as its slow one som systems. In schema compare I have ignore privileges ticked, but the query still runs

   6 votes

   Vote 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

5. International date formatting not working

   See: https://i.imgur.com/FvTda6n.png

   Sometime in version 9, 'datetime' fields in tables and queries format to the American standard, even though the formatting options show an example of International formatting, this is not applied

   4 votes

   Vote 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

6. Show/Hide additional document views

   With new DBForge update (2020), keyboard shortcut to show/hide additional document views is gone. Please add this feature back as it was extremely convenient to show/hide data results when writing long procedures.

   5 votes

   Vote 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

7. database name

   DATABASE: test
   DATABASE: Test
   DATABASE: tEsT

   dbForge identify the same database and can't find tables because the database differs to others as identified with the same name

   2 votes

   Vote 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
   AdminDevart (_, Devart) responded

   Could you please describe it in more detail?

   Also, you may need to change or remove a database name in the ‘Database’ field of the Database Connection Properties dialog box (right-click the connection in Database Explorer and select ‘Modify Connection…’ from the popup menu).

8. Start transaction read only

   When I editing storage procedure and I add START TRANSACTION READ ONLY;
   it is marked as error ';' expected

   8 votes

   Vote 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

9. Commandline Issues

   Whem importing from Access Database tables with a space in the name do not work at all. Also I just updated to the latest version hoping it would be fixed and now when the console prints out how many records have been imported, it prints on a new line instead of same line.

   3 votes

   Vote 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
   AdminDevart (_, Devart) responded

   > Whem importing from Access Database tables with a space in the name do not work at all.

   Could you please send us the imported file and let us know if you are importing into a new table or existing one?

   > Also I just updated to the latest version hoping it would be fixed and now when the console prints out how many records have been imported, it prints on a new line instead of same line.

   Could you please provide us a screenshot of this?

10. Combine ALTER Statements

    When making multiple modifications to a table, the generated SQL script contains multiple ALTER statements. For example, If I were to add 3 new columns to a table, the resulting script would be something like...

    ALTER TABLE table ADD COLUMN newcolumn1 INT;
    ALTER TABLE table ADD COLUMN newcolumn2 INT;
    ALTER TABLE table ADD COLUMN newcolumn3 INT;

    ... when these could actually be combined into a single ALTER statement like...

    ALTER TABLE table
    ADD COLUMN newcolumn1 INT,
    ADD COLUMN newcolumn2 INT,
    ADD COLUMN newcolumn3 INT;

    The 3 separate ALTER statements essentially take 3 times longer to run than the single combined ALTER statement. It might not seem like much, but this actually makes a gigantic difference when the table being altered is large, has many indexes, and/or has several things being altered... Imagine a large table that takes an hour to perform an ALTER on, and then having to unnecessarily multiply that hour by the number of things you're altering.

    The same thing happens when doing a schema comparison.

    When making multiple modifications to a table, the generated SQL script contains multiple ALTER statements. For example, If I were to add 3 new columns to a table, the resulting script would be something like...

    ALTER TABLE table ADD COLUMN newcolumn1 INT;
    ALTER TABLE table ADD COLUMN newcolumn2 INT;
    ALTER TABLE table ADD COLUMN newcolumn3 INT;

    ... when these could actually be combined into a single ALTER statement like...

    ALTER TABLE table
    ADD COLUMN newcolumn1 INT,
    ADD COLUMN newcolumn2 INT,
    ADD COLUMN newcolumn3 INT;

    The 3 separate ALTER statements essentially take 3 times longer to run than the single combined… more

    14 votes

    Vote 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

11. 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 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

12. Fix JSON view colors for dark themes

    Using the JSON view in dark themes is annoying as there is no way to configure foreground colors for numeric data types so they are displayed as black on black

    3 votes

    Vote 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

13. 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 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

14. EXPLAIN Partitions isn't working (but it used to in older versions)

    Version: 8.0.80 (Professional)
    Tried with MySQL 5.6 and 5.7

    Explain Partitions returns an error, but it works fine on the MySQL CLI.

    In dbForge I ran:
    EXPLAIN partitions SELECT * FROM log.log;

    And the error I got was:
    Table 'log.partitions' doesn't exist

    3 votes

    Vote 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
    AdminDevart (_, Devart) responded

    Hello,

    This issue is going to be fixed in the next product build. Currently, as a workaround, you can run statement using F5 button.

15. 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 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
    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 .

16. 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 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
    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 .

17. 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 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

18. Issue with Data Editor not respecting Edit mode set in settings after first edit.

    1. Options > Data Editor > General > Open Data Editor in read only mode
    2. Execute a SELECT statement. Data Editor shows up in Read Only Mode. Good.
    3. Flip Data Editor to Edit current table. Do one edit. Apply.
    4. (Optional: Flip Data Editor back to Read Only Mode)
    5. Execute a SELECT statement on ANY table. Data Editor shows up in Edit Mode on the current table. Disregarding both its last set state or System Setting
    3 votes

    Vote 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
    AdminDevart (_, Devart) responded

    We will fix this issue in one of the next product builds and will notify you once it’s available for downloading.

19. 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 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

20. При простое в работе (примерно через час) отключается таблица

    При простое в работе (примерно через час) отключается таблица.
    и постом при возобновление использования минимум ВСЕГДА ДВА раза пишет , одну и туже ошибку( Lost connection to MySQL server during query (......:3306) Table:....... ) если нажать обновить .

    а иногда вообще даже кнопка обновить исчезает и пишет что 0 записей хотя они есть. приходится переподключаться, исправьте пожалуйста, этот баг

    3 votes

    Vote 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
    AdminDevart (_, Devart) responded

    Вы можете попробовать увеличить значение в поле ‘Тайм-аут соединения’ на вкладке ‘Дополнительные’ окна ‘Свойства соединения базы данных’ (щёлкните правой кнопкой мыши на соединении в Проводнике и выберите ‘Изменить соединение…’ в контекстном меню). Значение, равное нулю, означает бесконечность.