Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain the different capabilities of using changeset types vs formatted SQL or SQL files. #72

Open
mbohls opened this issue Oct 22, 2020 · 1 comment
Labels
documentation Improvements or additions to documentation new-feature New feature or request product-doc written

Comments

@mbohls
Copy link

mbohls commented Oct 22, 2020

Examples of capabilities that are not possible in Formatted SQL:

  • Auto-generated rollbacks.

  • tagDatabase

  • labels

  • context

  • etc.

@carolhunt carolhunt added documentation Improvements or additions to documentation new-feature New feature or request product-doc written and removed hacktoberfest labels Dec 4, 2020
@doakd
Copy link

doakd commented Apr 7, 2021

labels and contexts are valid changeset attributes for formatted sql format.

https://docs.liquibase.com/concepts/basic/changeset.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation new-feature New feature or request product-doc written
Projects
None yet
Development

No branches or pull requests

4 participants