Skip to content

dbForge Studio for MySQL

dbForge Studio for MySQL is a universal set of MySQL GUI tools for database management, administration and development. It enables to create and execute queries, develop and debug MySQL routines, and automate MySQL database object management in the convenient environment.

http://www.devart.com/dbforge/mysql/studio/

dbForge Studio for MySQL

Categories

JUMP TO ANOTHER FORUM

3 results found

  1. When submitting routines to SVN through 'Source Control', the SQL Security option is lost

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Bugs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. If you editing a code of a routine (procedure or a function) but has not compiled it yet and then you add a parameter, the code of the routine gets refreshed and you loose all the code code you wrote before latest compilation. There was no such an issue in older versions of dbForge for MySQL (tested on 10.1.24)

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Bugs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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 utf8mb3generalci

    Reported RETURNS value (incorrect):
    RETURNS VARCHAR(80) CHARSET utf8mb4 COLLATE utf8mb4…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Bugs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?