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-schema-name

Why?#

Adding a schema name can harm portability of scripts and databases if schema name is not used consistently across all instances. The schema name should not really be needed at the script level, as when running Liquibase the user should have the correct schema access and/or default schema anyway.

The no-schema-name rule will fail for any changes that have a populated schemaName attribute.

Options#

No extra options.

Previous
« no-preconditions
Next
no-raw-sql »
  • Why?
  • Options
White Clarke Group Logo
Copyright © 2021 White Clarke Group