-
Notifications
You must be signed in to change notification settings - Fork 3
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
Validate the schema name #21
Comments
Yup. also still looking for valid schema names, can't find it as well. Will try to do more research after I do a hotfix |
ramontayag
added a commit
that referenced
this issue
Jul 14, 2013
ramontayag
added a commit
that referenced
this issue
Jul 14, 2013
ramontayag
added a commit
that referenced
this issue
Jul 14, 2013
ramontayag
added a commit
that referenced
this issue
Jul 14, 2013
* release/v0.5.0: bumps version Clean source and target after duplicating #18 Update changelog #21 Use schema name that is a string #21 Use schema name like a string #21 Validate schemas on create #21 Duplicator uses BuildsLoadCommand Refactor into method Use load command builder Upgrade easy_class_to_instance_method Extract dump command generation into class Do away with double negatives Removes attr_accessors from Storey::Duplicator and refactor arg to switch conversion in Storey::Duplicator Be more clear about path and dir Extract command line switch parsing to class Refactor for readability
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can't seem to find documentation on what schemas are valid, but what we know so far:
Questions:
@corroded, is this correct?
The text was updated successfully, but these errors were encountered: