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

drop-not-null-require-column-data-type

Why?#

When dropping a not-null constraint, some database vendors will fail if the columnDataType is not specified, while others will work fine. This can lead to problems if not caught soon enough.

This rule will fail if a dropNotNullConstaint is used without a columnDataType.

Options#

No extra options.

Previous
« create-table-remarks
Next
file-name-no-spaces »
  • Why?
  • Options
White Clarke Group Logo
Copyright © 2021 White Clarke Group