-
Notifications
You must be signed in to change notification settings - Fork 249
fix: exclude manually added columns from copy #598
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
Conversation
5ce31c8
to
4bae8b1
Compare
4bae8b1
to
7784037
Compare
7784037
to
f247916
Compare
f247916
to
350f583
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.
I think we should change this to look up types by column names, not just rely on the table prefix by attnum. That would be much more robust
Agreed. But if we do this, we must construct the |
b2f5e1d
to
712a710
Compare
712a710
to
fa13340
Compare
@cevian I updated the query. I don't really know how to write a test for this though, since you cant just add a column at any point in postgres, it's always added at the end. |
self.vectorizer.target_schema, | ||
self.vectorizer.target_table, | ||
target_columns, | ||
), | ||
) | ||
self.copy_types = [row[0] for row in await cursor.fetchall()] |
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.
there is no guarantee right now of the order of the results. The query should return the column name, type and then we can finangle things into the right order
9366b7a
to
312ebc4
Compare
No description provided.