-
Notifications
You must be signed in to change notification settings - Fork 4
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
don't allow commas in model and dataset names #700
don't allow commas in model and dataset names #700
Conversation
the migration file replaces dataset and model names with commas to underscores (and adds enough underscores to guarantee uniqueness). it then updates the model, dataset, and evaluation tables accordingly. here are screenshots of before and after running the migration command on some sample data |
|
||
DROP FUNCTION get_unique_name; | ||
|
||
COMMIT; |
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.
nit: Im not sure the COMMIT
is required since we don't use this elsewhere in the migration files.
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 you're right, i remvoed it
Does the migration run properly without |
not sure but i added an empty |
this was causing things like
get_evaluations
to fail since the query params are string separated model names