Unable to Debug on MariaDB
-
- Posts: 1
- Joined: Mon 17 Dec 2018 12:12
Unable to Debug on MariaDB
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
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
Re: Unable to Debug on MariaDB
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
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
Re: Unable to Debug on MariaDB
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:
You can send a reply straight to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .
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\
Re: Unable to Debug on MariaDB
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.
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.
Re: Unable to Debug on MariaDB
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.
We will fix this issue in one of the next product builds and will notify you once it's available for downloading.
Re: Unable to Debug on MariaDB
Latest update didn't solve this problem, right?
Re: Unable to Debug on MariaDB
Any ideas about the release of 8.2? I need this feature for debugging ... :(
Re: Unable to Debug on MariaDB
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.
Re: Unable to Debug on MariaDB
Any news about the update? I still need this feature...