Two Bugs

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
Andrew1178
Posts: 2
Joined: Fri 13 May 2016 15:02

Two Bugs

Post by Andrew1178 » Fri 13 May 2016 15:12

For my first bug, I cannot open DbForge. There are five of us using the DbForge application, we have purchased 11 licenses.

3 of us cannot even open DbForge unless we uninstall the application and reinstall. Even then we still get the same issue after about a day. All we do is open the application and we are greeted with this exception(pulled from error trace):

Message: Value cannot be null.
Parameter name: implementationType
Source: Autofac
TargetSite: Autofac.Builder.IRegistrationBuilder`3[System.Object,Autofac.Builder.ConcreteReflectionActivatorData,Autofac.Builder.SingleRegistrationStyle] RegisterType(Autofac.ContainerBuilder, System.Type, System.Object[])
HelpLink:
Type: System.ArgumentNullException
Place: 1

The second bug is slightly lesser. Say you have two tables:

tblClient - ClientID(INT), ClientName(VARCHAR(255))

tblDetail - DetailID(INT), DetailName(VARCHAR(255)), ClientID(INT)

And you have a query which looks like so:

SELECT * FROM tblClient as c
LEFT JOIN (
SELECT DetailID, ClientID FROM tblDetail
) d ON c.CLIENTID = d.ClientID

It will throw an exception with the following message:

This error happens because both tables have the column name ClientID. It works if you give the ClientID an alias in the join, still a bug none the less.

=========================
Exception Information
=========================
Message: Object reference not set to an instance of an object.
Source: Devart.DbForge.DataEditor
TargetSite: Void I4QjrsactH()
HelpLink:
Type: System.NullReferenceException
Place: 1
Stack:
at Devart.DbForge.DataTableEditorControl.I4QjrsactH()
at Devart.DbForge.DataTableEditorControl.ViewData(DataTable newDataTable)

alexa

Re: Two Bugs

Post by alexa » Mon 16 May 2016 10:35

3 of us cannot even open DbForge unless we uninstall the application and reinstall. Even then we still get the same issue after about a day. All we do is open the application and we are greeted with this exception(pulled from error trace):

Message: Value cannot be null.
Please perform the following:

1. Close dbForge Studio for MySQL.
2. Remove the following file

Code: Select all

%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\dbForge Studio for MySQL\uicache.dat
The second bug is slightly lesser. Say you have two tables:

tblClient - ClientID(INT), ClientName(VARCHAR(255))
We are aware of this issue and will fix it in the next product build. We will notify you once it's available for downloading.

Andrew1178
Posts: 2
Joined: Fri 13 May 2016 15:02

Re: Two Bugs

Post by Andrew1178 » Mon 16 May 2016 13:16

Please perform the following:

1. Close dbForge Studio for MySQL.
2. Remove the following file

Code: Select all

%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\dbForge Studio for MySQL\uicache.dat
Is this the accepted solution? Will there be a permanent fix in the future? If not, why isn't there more documentation on this? It could help others.

alexa

Re: Two Bugs

Post by alexa » Mon 16 May 2016 14:30

We've just replied to you on this issue by e-mail.

alexa

Re: Two Bugs

Post by alexa » Thu 10 Nov 2016 15:48

We would like to let you know that we have released dbForge Studio for MySQL, v7.2 where the issue you reported is fixed https://www.devart.com/dbforge/mysql/st ... nload.html

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

Post Reply