-
Notifications
You must be signed in to change notification settings - Fork 320
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
For single-table use cases, make it frictionless to update Metadata #2228
For single-table use cases, make it frictionless to update Metadata #2228
Conversation
4e62dbe
to
2bccb96
Compare
sdv/metadata/metadata.py
Outdated
@@ -173,7 +173,7 @@ def set_sequence_index(self, table_name, column_name): | |||
self._validate_table_exists(table_name) | |||
self.tables[table_name].set_sequence_index(column_name) | |||
|
|||
def set_sequence_key(self, table_name, column_name): | |||
def set_sequence_key(self, *args, **kwargs): |
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 for all of these we can just use the signature normally. For this one it would be set_sequence_key(self, column_name, table_name)
. I don't think we have to support a different order
sdv/metadata/metadata.py
Outdated
parameters = self._resolve_arguments(['column_name'], *args, **kwargs) | ||
super().update_column(**parameters) |
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 don't think we need this. Can we just list the args normally and then pass them in the correct order when calling super?
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.
lgtm
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.
Resolve #2213