59 results found

1. Function "greatest" causes error in project build

   When building a project, any SQL query that contains the "greatest" function is flagged with the error:

   The name 'greatest' does not exist in the current context

   (Using dbForge Studio for MySQL version 5.0.97.)

   7 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 →
   completed  ·  AdminDevart (_, Devart) responded

   This issue is fixed in the new version 6.0 of dbForge Studio for MySQL: http://www.devart.com/dbforge/mysql/studio/download.html

2. mariadb

   I have two mysql server. MariaDB 10.2 and Mysql 5.5.23
   When i make structure comparation i have such differences with default null fields:
   In MariaDB 10.2:
   guiname VARCHAR(200) DEFAULT 'NULL',
   description VARCHAR(2000) DEFAULT 'NULL',
   In Mysql:
   guiname VARCHAR(200) DEFAULT NULL,
   description VARCHAR(2000) DEFAULT NULL,

   And after sync these differences are remained

   7 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…)
   completed  ·  1 comment  ·  Bugs  ·  Delete…  ·  Admin →

3. Fix: Import/Export Environment

   Failure of any single change doesn't effect other settings (Project Path!)

   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 →
   completed  ·  AdminDevart (_, Devart) responded

   This issue is fixed in the new version 6.0 of dbForge Studio for MySQL: http://www.devart.com/dbforge/mysql/studio/

4. child windows docking

   if 2 or more windows is docking in 1 place, then it must restored in THIS place without dependence from it opening/closing order.

   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 →
   completed  ·  AdminDevart (_, Devart) responded

   This functionality was redesigned in the new version 6.0 of dbForge Studio for MySQL: http://www.devart.com/dbforge/mysql/studio/

5. Support version 5.7.15

   Dbforge studio can't connect to mysql 5.7.15.

   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 →
   completed  ·  AdminDevart (_, Devart) responded

   We would like to let you know that we have released dbForge Studio for MySQL, v7.1.20 where MySQL 5.7.15 is supported https://www.devart.com/dbforge/mysql/studio/download.html

   Thank you for your help in improving dbForge Studio for MySQL.

6. Application freeze on big database

   There is Magento database (~250 tables). After updation to 5.0.76 when I tryed open any table in thid db for editing application freeze for 0.5 minutes. Before (5.0.67) it will ok.

   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 →
   completed  ·  AdminDevart (_, Devart) responded

   This issue is supposed to be fixed in the new version 6.0 of dbForge Studio for MySQL: http://www.devart.com/dbforge/mysql/studio/

7. Make "AS" keyword auto-select in code completion dropdown.

   Most keywords seem to auto-select in the code completion dropdown as you type, with the only exception I've noticed so far being "AS" for column and table aliases (even though its the only choice in the list most of the time). Other short keywords such as "ON" and "BY" will auto-select, making it easy to type in lower case, get the suggestion dropdown, have it automatically selected for you, hit Enter to get the upper case equivalent and keep on going. With "AS" it breaks that pattern requiring you to hit down to select it in the list first.

   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…)
   1 comment  ·  Bugs  ·  Delete…  ·  Admin →
   completed  ·  AdminDevart (_, Devart) responded

   It’s not highlighted because this could be a part of a user-defined alias starting with AS…

   Though, you can manage this with the ‘Select items in the list even if a user input is expected’ option available in the ‘Text Editor → Code Completion → List Members’ branch of the ‘Options’ window that can be invoked by selecting ‘Tools → Options…’ from the main menu.

8. Cannot edit views if column no longer exists

   If you have a view that uses/selects columns that no longer exist, you cannot open the view to edit/fix the missing columns:

   View '<TABLE>.<VIEW>' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them

   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 →
   completed  ·  AdminDevart (_, Devart) responded

   Please check that you are using the latest build 6.3.358 https://www.devart.com/dbforge/mysql/studio/download.html

9. Issue with import of DATE/DATETIME fields from Excel 2007

   In latest version of dbForge while importing Excel 2007 file columns formatted as a date cannot be properly recognized as dates (they are recognized by dbForge as serial numbers) and due to this cannot be properly imported to the corresponding table fields. In older versions such bug hasn't had a place.
   Import date fields from Excel 2003 works fine in 6.3.330 version.

   BR

   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…)
   completed  ·  0 comments  ·  Bugs  ·  Delete…  ·  Admin →

10. Cannot see correctly the view's queries and update them on version: 6.1.142.

    Views does not seem to work well in the new release..

    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 →
    completed  ·  AdminDevart (_, Devart) responded

    This issue will be fixed in the next product build.

11. GROUP_CONCAT

    Don't show GROUP_CONCAT in queries.

    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…)
    completed  ·  3 comments  ·  Bugs  ·  Delete…  ·  Admin →

12. When searching objects (cntrl+D,F), searching in tables data and you get a lot of results, that do not fit in result windows, a scroll bar i

    When searching objects (cntrl+D,F), searching in tables data and you get a lot of results, that do not fit in result windows, a scroll bar did not show up. It needs to click on the place where it should be, only then it appears.

    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…)
    completed  ·  0 comments  ·  Bugs  ·  Delete…  ·  Admin →

13. Process left in memory after program closes.

    Each new run left another instance. Eat memory, lock updates. All 7.x versions, last 7.0.52.0 too.

    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…)
    completed  ·  0 comments  ·  Bugs  ·  Delete…  ·  Admin →

14. Using "create script as + create" generates an invalid script in dbForge Studio for MySQL

    Using "create script as + create" generates an invalid script in dbForge Studio for MySQL

    This happens when the default value on a field is currenttimestamp(6) ON UPDATE currenttimestamp(6)

    Example of what gets generated.

    CREATE TABLE test.junkola (
    Id int(11) NOT NULL AUTOINCREMENT,
    RowVersion datetime(6) NOT NULL DEFAULT 'CURRENTTIMESTAMP(6)' ON UPDATE CURRENT_TIMESTAMP (6),
    PRIMARY KEY (Id)
    )

    The QUOTES around 'current_timestamp(6)' do not compile in your tool.

    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…)
    completed  ·  2 comments  ·  Bugs  ·  Delete…  ·  Admin →

15. Fix data compare by text key

    Beginning with dbForge Studio of MySQL 7.3 (possibly earlier), and continuing into the recently released 7.4.201, I am seeing some incorrect results when using the data comparison feature.

    Specifically, it seems to happen when I compare data based on a textual key column rather than the integer-based primary key. Here is an simple example that will produce incorrect results with 7.4.201:

    -- ###########################################
    -- Server 1

    CREATE TABLE test (
    id INT(10) UNSIGNED NOT NULL AUTOINCREMENT,
    key VARCHAR(255) NOT NULL,
    value VARCHAR(80) NOT NULL,
    PRIMARY KEY (id),
    UNIQUE INDEX uniquekey (key)
    )
    ENGINE = INNODB,
    CHARACTER SET utf8,
    COLLATE utf8generalci;

    INSERT INTO test(id, key, value) VALUES
    (1, 'PROBLEM12', 'Not Only in Source, Not PROBLEM123456789'),
    (2, 'PROBLEM123456789', 'Not Only in Target, Not Different'),
    (3, 'NEW1', 'NEW1name'),
    (4, 'NEW2', 'NEW2name');

    -- ###########################################
    -- Server 2

    CREATE TABLE test (
    id INT(10) UNSIGNED NOT NULL AUTOINCREMENT,
    key VARCHAR(255) NOT NULL,
    value VARCHAR(80) NOT NULL,
    PRIMARY KEY (id),
    UNIQUE INDEX uniquekey (key)
    )
    ENGINE = INNODB,
    CHARACTER SET utf8,
    COLLATE utf8generalci;

    INSERT INTO test(id, key, value) VALUES
    (1, 'PROBLEM12', 'Not Only in Source, Not PROBLEM123456789'),
    (2, 'PROBLEM123456789', 'Not Only in Target, Not Different');

    After creating the table and data on two servers, run the "New Data Comparison" tool and select the Test table. Under the Column Mapping dialog:

    id: (uncheck key, and compare, leaving only sync checked)
    key: (check key, leaving compare and sync checked)
    value: (no change, leave compare and sync checked)

    Run the compare.

    Under the "Only in Source" results, it will incorrectly include the record with key=PROBLEM12. Under Different Records, it will incorrectly display record id 1 as if it had the key belonging to record id 2. Under "Only in Target", it will incorrectly include the record with key=PROBLEM_123456789.

    Naturally, this is very concerning, as it could lead to data corruption when deploying changes from one server to another. Also, the synchronization script contains results which are obviously incorrect and will produce and error (given the unique constraint on the key column).

    --

    -- Deleting data from table test

    DELETE FROM test WHERE key = 'PROBLEM_123456789';

    --

    -- Updating data of table test

    UPDATE test SET id = 2, value = 'Not Only in Target, Not Different' WHERE key = 'PROBLEM_123456789';

    --

    -- Inserting data into table test

    INSERT INTO test(key, id, value) VALUES
    ('NEW1', 3, 'NEW1name'),
    ('NEW2', 4, 'NEW2name'),
    ('PROBLEM12', 1, 'Not Only in Source, Not PROBLEM_123456789');

    This will cause the UPDATE to not have any records to update, and then throw a unique key constraint error when attempting to insert a duplicate key for "PROBLEM12".

    Beginning with dbForge Studio of MySQL 7.3 (possibly earlier), and continuing into the recently released 7.4.201, I am seeing some incorrect results when using the data comparison feature.

    Specifically, it seems to happen when I compare data based on a textual key column rather than the integer-based primary key. Here is an simple example that will produce incorrect results with 7.4.201:

    -- ###########################################
    -- Server 1

    CREATE TABLE test (
    id INT(10) UNSIGNED NOT NULL AUTOINCREMENT,
    key VARCHAR(255) NOT NULL,
    value VARCHAR(80) NOT NULL,
    PRIMARY KEY (id),
    UNIQUE INDEX uniquekey (key)
    )
    ENGINE = INNODB,
    CHARACTER… more

    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…)
    completed  ·  0 comments  ·  Bugs  ·  Delete…  ·  Admin →

16. TIMESTAMP field editing with a calendar

    In the new version for some reason you can not

    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 →
    completed  ·  AdminDevart (_, Devart) responded

    This issue is fixed in the new build 6.0.113 of dbForge Studio Beta for MySQL: http://www.devart.com/dbforge/mysql/studio/download.html

17. Not open some of the procedures for editing.

    Not open some of the procedures, don't know what it is, but with a short name opening all the time, and long not open > ~ 40 characters (can cause). The error message "Cannot parse the source code"

    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 →
    completed  ·  AdminDevart (_, Devart) responded

    We would like to let you know that we have released a new build 6.3.339 of dbForge Studio for MySQL where the issue you reported is fixed http://www.devart.com/dbforge/mysql/studio/download.html

    Thank you for your help in improving dbForge Studio for MySQL.

18. Separate DEFINER and SQL SECURITY in exclude backup options

    It only makes sense to combine these two options when SQL SECURITY is set to DEFINER. In the other case (INVOKER) it will cause a problem if the DEFINER is specified when restoring the database to a different environment - user will not exist or will not have the right privileges. "Exclude DEFINER" and "Exclude SQL SECURITY" should be two separate options when backing up a database.

    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…)
    completed  ·  2 comments  ·  Bugs  ·  Delete…  ·  Admin →

19. Support for fractional datetime

    since Mysql 5.6.4 (2011), there is a support for fractional datetime and timestamp.

    cf. http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

    select now(6) should return 2015-07-16 23:48:52.720993 (like with phpmyadmin) and not 16/07/2015 23:46:52

    or better , it should return the localized version 16/07/2015 23:46:52.720993

    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 →
    completed  ·  AdminDevart (_, Devart) responded

    This can be setup as follows:

    1. Select ‘Tools → Options’ from the main menu. The ‘Options’ window opens.
    2. Navigate to the ‘Data Editor → Formatting’ branch.
    3. Select ‘DateTime’ from the ‘Data type’ dropdown menu.
    4. In the ‘Predefined Formats’ list, select ‘General date/time (longtime with microseconds)’.
    5. Click ‘OK’.

20. When editing the build order, the changes should actually be saved to the xxx.mydev file.

    when adding a new table to a project, it is added to the bottom of the build order list. If I edit the list thru the project properties > build order tab, the order changes are not persisted. I have had to edit the xxx.mydev file manually (outside of visual studio) to get the build to create the .sql file with the table listed in the right order based on foreign key dependencies.

    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 →
    completed  ·  AdminDevart (_, Devart) responded

    Build Order is detected automatically.