-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Column Exclusion #601
Column Exclusion #601
Conversation
80a25b1
to
aa72c90
Compare
f7a4072
to
834ea32
Compare
5800dc8
to
11f910d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@serprex can we think about how we can test this change?
e6607f7
to
543524c
Compare
Edgecase: with schema changes, drop excluded column. Expectation: ignore. Then add excluded column back. Expectation: continue excluding? |
Yes, continue excluding. Also currently mirrors are static, I think eventually we would want to make them dynamic, where a user can exclude more columns, but thats a problem for another day. |
ee04651
to
918f2ce
Compare
a052e93
to
94ab6f8
Compare
Currently only extends things to handle exclude field from PeerDB-io/sqlparser-rs#21 but doesn't do anything with it
…s but maybe there's something to talk about here
… & had to rely on git checkout oldcommit to retrieve the old tree which thankfully had not been collected by git's gc yet
…ups. Now it works
setup_flow: copy tableSchema
538973d
to
8ff216c
Compare
8ff216c
to
4caf513
Compare
If a mirror is created with exclusions omit those columns from schema of target table Syntax is in `TABLE MAPPING` of `CREATE MIRROR`, `exclude:[col1,col2]` Ignores column appearing in schema changes too Fixes #428
If a mirror is created with exclusions omit those columns from schema of target table
Syntax is in
TABLE MAPPING
ofCREATE MIRROR
,exclude:[col1,col2]
Ignores column appearing in schema changes too
Fixes #428