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
When we denest a column and then handle things like naming collisions, you can end up with very confusing structures when trying to map it all back to the input data.
To aid in this, we could set some helpful string comments/descriptions onto each column's COMMENT in PostgreSQL. Something like:
# Singer Target Postgres
This table was denested from (t0, t1, t2, ...)
This column was denested from (c0, c1, ...)
You can join this back to it's original parent via:
SOME-SQL-HERE
Motivation
When we denest a column and then handle things like naming collisions, you can end up with very confusing structures when trying to map it all back to the input data.
To aid in this, we could set some helpful string comments/descriptions onto each column's
COMMENT
in PostgreSQL. Something like:etc.
Suggested Musical Pairing
https://soundcloud.com/hiatus-kaiyote/nakamarra-1
The text was updated successfully, but these errors were encountered: