EDIT: Not sure what's going on - I deleted this post, but a bot has responded to it. Note this issue is tied to the error where the wrong value displays - I've fixed it - so it's not a dbForge issue logically - it's a bug where dbForge is reporting the wrong value. Note to Moderator - you can delete this post.
Not sure things get more wonky than this; the screenshot says it all. When I try to debug this code, it steps into the next line even though var_process_id is 0. Makes absolutely no sense at all; continues nonstop to process the loop in debug mode. This is a red flag bug/error as it represents a core logic flow issue with the debugging system.
dbForge Studio 2019 for MySQL Debugging Logic Error
dbForge Studio 2019 for MySQL Debugging Logic Error
Last edited by Requnix on Tue 21 Jan 2020 02:08, edited 1 time in total.
Re: dbForge Studio 2019 for MySQL Debugging Logic Error
We will fix the issue with incorrect value displaying in version 9.0.