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.

Sign up for GitHub

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

Fix CHAGE_HISTORY typo in devops_dcm_schemachange_azure_devops.md #1424

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix CHAGE_HISTORY typo in devops_dcm_schemachange_azure_devops.md #1424

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...rc/devops_dcm_schemachange_azure_devops/devops_dcm_schemachange_azure_devops.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -340,7 +340,7 @@ Now that your first database migration has been deployed to Snowflake, log into
You should now see a few new objects in your `DEMO_DB` database:

- A new schema `DEMO` and table `HELLO_WORLD` (created by the first migration script from step 4)
- A new schema `SCHEMACHANGE` and table `CHAGE_HISTORY` (created by schemachange to track deployed changes)
- A new schema `SCHEMACHANGE` and table `CHANGE_HISTORY` (created by schemachange to track deployed changes)

Take a look at the contents of the `CHANGE_HISTORY` table to see where/how schemachange keeps track of state. See the [schemachange README](https://github.com/Snowflake-Labs/schemachange) for more details.

Expand Down