From 7abefeb47a3af6e69cc05bbadf55c1e9ef7188dc Mon Sep 17 00:00:00 2001 From: Evgeny Kulikov Date: Fri, 6 Oct 2023 14:56:48 +0300 Subject: [PATCH] Fix a typo in docs/README.md (#172) --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index 8f50127d..824e6cf8 100644 --- a/docs/README.md +++ b/docs/README.md @@ -40,7 +40,7 @@ ![migration flow](img/migration-flow@2x.png) -During the migration start phase, `pgroll` will perform only additive changes to the database schema. This includes: creating new tables, adding new columns, and creating new indexes. In the cases were a required change is not backwards compatible, `pgroll` will take the necessary steps to ensure that the current schema is still valid. For example, if a new column is added to a table with a `NOT NULL` constraint, `pgroll` will backfill the new column with a default value. +During the migration start phase, `pgroll` will perform only additive changes to the database schema. This includes: creating new tables, adding new columns, and creating new indexes. In the cases where a required change is not backwards compatible, `pgroll` will take the necessary steps to ensure that the current schema is still valid. For example, if a new column is added to a table with a `NOT NULL` constraint, `pgroll` will backfill the new column with a default value. After a successful migration start, the database will contain two versions of the schema: the old version and the new version. The old version of the schema is still available to client applications. This allows client applications to be updated to use the new version of the schema without any downtime.