From 83ed8fb49d28923874cf53919ca15c2a198edd3c Mon Sep 17 00:00:00 2001 From: kostasb Date: Mon, 29 Jul 2024 10:12:25 +0300 Subject: [PATCH 1/3] update limitation paragraphs in pg docs --- 020-Connect/010-Postgres/001-direct-access.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/020-Connect/010-Postgres/001-direct-access.mdx b/020-Connect/010-Postgres/001-direct-access.mdx index 495c2265..d1c76a22 100644 --- a/020-Connect/010-Postgres/001-direct-access.mdx +++ b/020-Connect/010-Postgres/001-direct-access.mdx @@ -285,9 +285,9 @@ Concurrent connections are limited by [plan](/docs/concepts/pricing#pricing-plan Branch migrations are not supported yet. In databases that support direct Postgres access, you can create new branches but they cannot be merged together. This capability will become available later on. -### ORM native migrations are unsupported +### Schema files -Currently we recommend using `xata pull [branchname]`, `xata push [branchname]` or the UI's migration editor to manage your schema changes. ORM native migrations (such as those in Django, Prisma or the like) will possibly have issues during the beta. Our goals are to increase support as we move toward general availability. +CLI commands that apply schema files (`xata schema upload schema.json`, `xata init --schema=schema.json`) are not supported in Postgres-enabled databases. The recommended method to [export](/docs/postgres#export) and [import](/docs/postgres#import) a certain schema is via standard postgres tools (`psql`,`pg_dump`,`pg_restore`). For example, you can add the `--schema-only` parameter to `pg_dump` to export just the schema and no data. ## Column metadata From 80327551852871608927c8decec6014d69913063 Mon Sep 17 00:00:00 2001 From: kostasb Date: Mon, 29 Jul 2024 10:14:46 +0300 Subject: [PATCH 2/3] capitalize --- 020-Connect/010-Postgres/001-direct-access.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/020-Connect/010-Postgres/001-direct-access.mdx b/020-Connect/010-Postgres/001-direct-access.mdx index d1c76a22..4680803c 100644 --- a/020-Connect/010-Postgres/001-direct-access.mdx +++ b/020-Connect/010-Postgres/001-direct-access.mdx @@ -287,7 +287,7 @@ Branch migrations are not supported yet. In databases that support direct Postgr ### Schema files -CLI commands that apply schema files (`xata schema upload schema.json`, `xata init --schema=schema.json`) are not supported in Postgres-enabled databases. The recommended method to [export](/docs/postgres#export) and [import](/docs/postgres#import) a certain schema is via standard postgres tools (`psql`,`pg_dump`,`pg_restore`). For example, you can add the `--schema-only` parameter to `pg_dump` to export just the schema and no data. +CLI commands that apply schema files (`xata schema upload schema.json`, `xata init --schema=schema.json`) are not supported in Postgres-enabled databases. The recommended method to [export](/docs/postgres#export) and [import](/docs/postgres#import) a certain schema is via standard Postgres tools (`psql`,`pg_dump`,`pg_restore`). For example, you can add the `--schema-only` parameter to `pg_dump` to export just the schema and no data. ## Column metadata From 4e6a21d6a73a7c7bef2279c7de1e2d01b42f9745 Mon Sep 17 00:00:00 2001 From: kostasb Date: Mon, 29 Jul 2024 10:16:11 +0300 Subject: [PATCH 3/3] remove schema file paragraph --- 020-Connect/010-Postgres/001-direct-access.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/020-Connect/010-Postgres/001-direct-access.mdx b/020-Connect/010-Postgres/001-direct-access.mdx index 4680803c..e1ea5914 100644 --- a/020-Connect/010-Postgres/001-direct-access.mdx +++ b/020-Connect/010-Postgres/001-direct-access.mdx @@ -285,10 +285,6 @@ Concurrent connections are limited by [plan](/docs/concepts/pricing#pricing-plan Branch migrations are not supported yet. In databases that support direct Postgres access, you can create new branches but they cannot be merged together. This capability will become available later on. -### Schema files - -CLI commands that apply schema files (`xata schema upload schema.json`, `xata init --schema=schema.json`) are not supported in Postgres-enabled databases. The recommended method to [export](/docs/postgres#export) and [import](/docs/postgres#import) a certain schema is via standard Postgres tools (`psql`,`pg_dump`,`pg_restore`). For example, you can add the `--schema-only` parameter to `pg_dump` to export just the schema and no data. - ## Column metadata Xata uses SQL comments on columns to track some replication-related metadata about certain types of columns. These comments are only ever present on columns created using the Xata UI, and only on certain types of columns.