From 8e7522a91beca8fdb2be0f4964ae21bcbf670a28 Mon Sep 17 00:00:00 2001 From: Charlie Gerrior Date: Wed, 3 Nov 2021 14:43:29 -0400 Subject: [PATCH 1/2] fixes minor typo --- src/connections/storage/warehouses/schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/storage/warehouses/schema.md b/src/connections/storage/warehouses/schema.md index d5d17c1c99..de536c63ec 100644 --- a/src/connections/storage/warehouses/schema.md +++ b/src/connections/storage/warehouses/schema.md @@ -258,7 +258,7 @@ analytics.track('Register', { Then you can expect to see columns named `plan` and `account_type` as well as the default `event`, `id`, and so on. That way, you can write queries against any of the custom data sent in track calls. > info "Note" -> Because `properties` and `traits` are added as un-prefixed columns to your tables, there is a chance of collision with our reserved column names. For this reason, properties with the same name as reserved column name (for example. `user_id`) are discarded. +> Because `properties` and `traits` are added as un-prefixed columns to your tables, there is a chance of collision with our reserved column names. For this reason, properties with the same name as reserved column name (for example, `user_id`) are discarded. Your event tables are one of the more powerful datasets in Segment SQL. They allow you to see which actions users perform when interacting with your product. From 649206c56b58e133a08f3beb09fcaa1366b90066 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Thu, 4 Nov 2021 09:13:19 -0700 Subject: [PATCH 2/2] Update src/connections/storage/warehouses/schema.md --- src/connections/storage/warehouses/schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/storage/warehouses/schema.md b/src/connections/storage/warehouses/schema.md index de536c63ec..288968c3d0 100644 --- a/src/connections/storage/warehouses/schema.md +++ b/src/connections/storage/warehouses/schema.md @@ -258,7 +258,7 @@ analytics.track('Register', { Then you can expect to see columns named `plan` and `account_type` as well as the default `event`, `id`, and so on. That way, you can write queries against any of the custom data sent in track calls. > info "Note" -> Because `properties` and `traits` are added as un-prefixed columns to your tables, there is a chance of collision with our reserved column names. For this reason, properties with the same name as reserved column name (for example, `user_id`) are discarded. +> Because Segment adds `properties` and `traits` as un-prefixed columns to your tables, there is a chance the names can collide with the reserved column names. For this reason, Segment discards properties with the same name as the reserved column name (for example, `user_id`). Your event tables are one of the more powerful datasets in Segment SQL. They allow you to see which actions users perform when interacting with your product.