Menu
White Clarke GroupLiquibase Linter
SetupRulesBlogGitHub
White Clarke GroupLiquibase Linter
  • Setup
  • Rules
  • Blog
  • GitHub
  • Setup
    • Install
    • Configure
    • Retrofitting
  • Rules
    • Using Rules
    • Custom Rules
      • Implementing a Custom Rule
    • Core Rules
      • create-column-no-define-primary-key
      • create-column-nullable-constraint
      • create-column-remarks
      • create-index-name
      • create-table-remarks
      • drop-not-null-require-column-data-type
      • file-name-no-spaces
      • file-not-included
      • foreign-key-name
      • has-comment
      • has-context
      • illegal-change-types
      • isolate-ddl-changes
      • modify-data-enforce-where
      • modify-data-starts-with-where
      • no-duplicate-includes
      • no-preconditions
      • no-schema-name
      • no-raw-sql
      • object-name
      • object-name-length
      • primary-key-name
      • schema-name
      • separate-ddl-context
      • table-name
      • table-name-length
      • unique-constraint-name
      • valid-context
Version: Next

no-raw-sql

Why?#

Liquibase supports a lot of different changes, and raw sql change types are only useful for edge cases or complex cases. By default changes should be done using Liquibase’s automated refactoring tags and not raw sql.

This rule will fail if either <sql> or <sqlFile> change types are used.

Options#

No extra options.

Example Usage#

{
"rules": {
"no-raw-sql": true
}
}
Previous
« no-schema-name
Next
object-name »
  • Why?
  • Options
  • Example Usage
White Clarke Group Logo
Copyright © 2021 White Clarke Group