Code Analysis

Code Analysis for Oracle 1 release notes

1.14.4919 - May 06 2021

Improvements

  • Upgraded to gudusoft.gsqlparser 3.3.3.1

Fixes

  • CAO should no longer fail to parse inline addition operations.

1.13.4855 - December 10 2020

Improvements

  • Upgrade to .NET 5

  • Upgrade to gudusoft.gsqlparser 3.3.2.5

1.12.4704 - September 29 2020

Improvements

  • Makes Code Analysis for Oracle available as a Docker image

Changes:

  • Replace Deployment Suite for Oracle branding with Redgate Deploy - Oracle

1.11.4684 - September 25 2020

Improvements

  • Improved logging for visibility and diagnosis of sql parsing

Changes:

  • Breaking Change: Now requires -IAcceptTheEula or /IAcceptTheEula flag to be set to run

1.10.4428 - June 17 2020

Improvements

  • report version number at startup in log file
  • remove version being reported as 'PREVIEW' in output and update copyright year

1.9.4417 - May 20 2020

Improvements

  • Improve logging output from third-party sql parsing library
  • When errors do occur, output suggests enhanced logging option (-debug or /debug) to user for more detail

1.8.4400 - May 9 2020

Fixes

  • Fixed an issue where SQL files containing chained method calls could not be parsed

  • Fixed an issue where SQL files containing DDL statements specifying the data type "CHARACTER VARYING(n)" could not be parsed

  • Fixed an issue where SQL files containing CREATE TABLE statements specifying the "GENERATED AS IDENTITY" column property could not be parsed

1.7.4386 - April 30 2020

Fixes

  • Fixed an issue where if a CAO settings file was passed to the command line, only a single rule would be selected.

1.6.4375 - April 7 2020

Improvements

  • Now report the exit code in the log file.

  • Improved reliability

1.5.4281 - March 12 2020

Improvements

  • Improved exit codes:

    • 0 - CAO returned successfully and found no errors or warnings in the sql

    • 1 - CAO did not exit cleanly - please see the logs

    • 2 - CAO had one or more internal errors, meaning individual files failed to be analysed

    • 3 - CAO found one or more errors in the sql it analysed

    • 4 - CAO reported one or more warnings in the sql it analysed

  • Extra Debug option available for logging available through -Debug, /Debug, -d or /d

Changes

  • SQL Parser library upgraded to latest available (3.3.0.5)

1.4.4272 - March 12 2020 (Linux and Mac only)

Improvements

  • Improved exit codes:

    • 0 - CAO returned successfully and found no errors or warnings in the sql

    • 1 - CAO did not exit cleanly - please see the logs

    • 2 - CAO had one or more internal errors, meaning individual files failed to be analysed

    • 3 - CAO found one or more errors in the sql it analysed

    • 4 - CAO reported one or more warnings in the sql it analysed

  • Extra Debug option available for logging available through -Debug, /Debug, -d or /d

Changes

  • SQL Parser library upgraded to latest available (3.3.0.5)

1.3.4156 - February 25 2020

Improvements

  • Log file name is now easier to read.

Fixes

  • Redgate executables are now properly signed.

1.2.0.4104 - February 19 2020

Improvements

  • SchemaRequired rule no longer requires a schema to be specified for DUAL table.

1.1.0 - January 9 2020

Fixes

  • Fixed some bugs with the rules

1.0 - December 10 2019

Improvements

  • Can now specify naming conventions for Tables.

0.1 (Preview) January 24th 2019

  • New report output. Use /outfile:<results>.html to create an html report instead of xml.
  • Parser errors output output stack trace to cao.exceptions  and no longer to console. By default parser errors don't cause a fail exit code. To enable this, use -reporterroroninternalexception
  • Linux compatibility
  • Five new rules added: AvoidDistinctUseUnionAllUseHavingWithGroupBy, CreateTableStatement, TypeNameConvention (see documentation for more detail)
  • Initial set of code analysis rules available on Windows command line

Didn't find what you were looking for?