A few days ago, I discovered that ZPA was not handling quoted identifiers properly. Specifically, the component responsible for creating the symbol table was not correctly identifying and counting the usage of quoted identifiers. This led to inaccurate results, which could affect the quality of the code analysis.

I intend to start a series of posts called "DevNotes" here. This series will be a collection of posts where I share some discoveries and experiences while developing ZPA and learning even more about PL/SQL and Oracle SQL.

In this series, I will cover a variety of topics related to PL/SQL, including:

• Code analysis techniques: how ZPA analyzes PL/SQL code and the challenges involved.
• Code analysis: methods to analyze PL/SQL code to improve performance and maintainability.
• Best practices: tips and tricks for writing efficient and clean PL/SQL code.

ZPA 3.5.1 is out!

This is a bug fix release that addresses an issue with coverage import for package bodies declared in the same file as the package specification.

For detailed release notes, please visit the full changelog.

ZPA 3.5.0 is out! This version brings several new features, improvements, and bug fixes.

• SonarQube compatibility: Compatible with SonarQube 9.9 LTA Community Edition and newer.
• utPLSQL integration: First-class support for test and coverage reports generated by utPLSQL.
• New grammar support: Added support for all SQL/JSON functions.
• Numerous bug fixes and performance improvements.

For detailed release notes, please visit the full changelog.