Unable to Debug on MariaDB

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
RoadRunner69
Posts: 1
Joined: Mon 17 Dec 2018 12:12

Unable to Debug on MariaDB

Post by RoadRunner69 » Mon 17 Dec 2018 12:17

Hello.

If I want to start to debug my stored functions and procedures I alway get the same message. Illegal parameter data type bigint for operation 'get_lock'. I use dbforge 8.0.124 and MariaDB 10.3.11 What I do wrong?

Thank you

marlik
Posts: 5
Joined: Thu 20 Dec 2018 07:49

Re: Unable to Debug on MariaDB

Post by marlik » Thu 20 Dec 2018 07:54

Hi,

I got the same problem. Seems to be a bug in dbForge Studio for MySQL (8.0.124) working with MariaDB 10.3/10.2. I send a support request, hoping to fix this.

Greetings,
MaRlik

alexa

Re: Unable to Debug on MariaDB

Post by alexa » Thu 20 Dec 2018 11:02

Could you please provide us a screenshot of the error and perform the following:
1. Select 'Tools -> Options...' from the main menu. The 'Options' window opens.
2. Navigate to the 'Environment -> Output' branch.
3. Select the 'Write queries sent by the program to the SQL Log' and 'Log application errors' options.
4. Unselect the 'Delete application log after closing' option. Click 'OK'.
5. Reproduce the issue and send us the *.log file with the latest date from the directory:

Code: Select all

%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\dbForge Studio for MySQL\
You can send a reply straight to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .

marlik
Posts: 5
Joined: Thu 20 Dec 2018 07:49

Re: Unable to Debug on MariaDB

Post by marlik » Fri 21 Dec 2018 09:19

Mail is sent to you.

It seems, this is a general issue working with a MariaDB 10.3 Server. I tried some older versions, like dbForge for MySQL 7.4.201 / 8.0.40 / 8.0.80 / 8.0.108 / 8.0.124 and non of them is working with MariaDB 10.3 Servers.

If I try to debug on a MariaDB 10.2 Server, it's working.

So the work around is, if possible, debug on an older MariaDB Server.

alexa

Re: Unable to Debug on MariaDB

Post by alexa » Fri 21 Dec 2018 14:29

Thank you for the reply.

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

marlik
Posts: 5
Joined: Thu 20 Dec 2018 07:49

Re: Unable to Debug on MariaDB

Post by marlik » Wed 16 Jan 2019 11:35

Latest update didn't solve this problem, right?

alexa

Re: Unable to Debug on MariaDB

Post by alexa » Thu 17 Jan 2019 11:39

This is planned to be fixed in version 8.2.

marlik
Posts: 5
Joined: Thu 20 Dec 2018 07:49

Re: Unable to Debug on MariaDB

Post by marlik » Fri 29 Mar 2019 10:05

Any ideas about the release of 8.2? I need this feature for debugging ... :(

alexa

Re: Unable to Debug on MariaDB

Post by alexa » Mon 01 Apr 2019 11:22

It should be released in June-July.

jarguess
Posts: 1
Joined: Mon 20 May 2019 07:02

Re: Unable to Debug on MariaDB

Post by jarguess » Mon 20 May 2019 07:07

I've been using the express edition. I purchased the standard edition today specifically for this feature. Now I have to find a new product because I cant wait a month or two. Really disappointed in my purchase and will be seeking a refund.

alexa

Re: Unable to Debug on MariaDB

Post by alexa » Wed 22 May 2019 14:51

We have sent you a custom build with the fix by e-mail.

marlik
Posts: 5
Joined: Thu 20 Dec 2018 07:49

Re: Unable to Debug on MariaDB

Post by marlik » Wed 03 Jul 2019 14:57

Any news about the update? I still need this feature...

alexa

Re: Unable to Debug on MariaDB

Post by alexa » Wed 03 Jul 2019 18:14

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

Post Reply