From 3b02b182eee9d36f27c79989bce31e13b3d2fc01 Mon Sep 17 00:00:00 2001 From: Viktoria <69359798+no-name16@users.noreply.github.com> Date: Sun, 19 Mar 2023 07:44:50 +0100 Subject: [PATCH] Correct a spelling mistake --- database/clickhouse/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/database/clickhouse/README.md b/database/clickhouse/README.md index 14de52931..a3cea9298 100644 --- a/database/clickhouse/README.md +++ b/database/clickhouse/README.md @@ -23,4 +23,4 @@ * Clickhouse cluster mode is not officially supported, since it's not tested right now, but you can try enabling `schema_migrations` table replication by specifying a `x-cluster-name`: * When `x-cluster-name` is specified, `x-migrations-table-engine` also should be specified. See the docs regarding [replicated table engines](https://clickhouse.tech/docs/en/engines/table-engines/mergetree-family/replication/#table_engines-replication). * When `x-cluster-name` is specified, only the `schema_migrations` table is replicated across the cluster. You still need to write your migrations so that the application tables are replicated within the cluster. -* If you want to create database inside the migration, you should know, that table which will manage migrations `schema-migrations table` will be in `deafault` table, so you can't use `USE ` inside migration. In this case you may not specify the database in the connection string (example you can find [here](examples/migrations/003_create_database.up.sql)) \ No newline at end of file +* If you want to create database inside the migration, you should know, that table which will manage migrations `schema-migrations table` will be in `default` table, so you can't use `USE ` inside migration. In this case you may not specify the database in the connection string (example you can find [here](examples/migrations/003_create_database.up.sql))