You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/storage/warehouses/schema.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -258,7 +258,7 @@ analytics.track('Register', {
258
258
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.
259
259
260
260
>info "Note"
261
-
>Because`properties` and`traits`are addedas un-prefixed columns to your tables, there is a chanceof collision with ourreserved column names. For this reason, properties with the same name as reserved column name (for example,`user_id`) are discarded.
261
+
>BecauseSegment adds`properties` and`traits` as un-prefixed columns to your tables, there is a chancethe names can collide withreserved column names. For this reason,Segment discardsproperties with the same name asthereserved column name (for example,`user_id`).
262
262
263
263
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.