Version: 9.0.338
This happens quite often - I'll have a variable in a Stored Procedure that is not declared (and used in just one area by mistake), yet the IDE doesn't detect it as invalid. This is the perfect example:
Note the SP saves just fine as well. Given the IDE will catch other variable issues (where they don't exist), this appears to be a bug.
Bug - dbForge Studio 2020 MySQL Enterprise - IDE not detecting invalid variables in Stored Procedures
Re: Bug - dbForge Studio 2020 MySQL Enterprise - IDE not detecting invalid variables in Stored Procedures
This feature is already in our roadmap for the next product versions.
Re: Bug - dbForge Studio 2020 MySQL Enterprise - IDE not detecting invalid variables in Stored Procedures
What is "next product version"? Is it a patch, or a completely new version/revision? When could we see this functionality added by?
Note anyone who purchases your product will expect this to be working already, so I consider it to be a substantial bug that contradicts expected features. In other words, I think it should be high priority and patched ASAP. It's certainly causing problems for me with our project.
Note anyone who purchases your product will expect this to be working already, so I consider it to be a substantial bug that contradicts expected features. In other words, I think it should be high priority and patched ASAP. It's certainly causing problems for me with our project.
Re: Bug - dbForge Studio 2020 MySQL Enterprise - IDE not detecting invalid variables in Stored Procedures
We are planning to release the version with the fix in about six months' time.