-
Notifications
You must be signed in to change notification settings - Fork 39
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
TableSchema to CREATE TABLE? #186
Comments
I think this should be possible (though it won't be able to set up things like |
I'm happy to add my own keys! |
I tried to implement this today (in library code), but AFAICT there simply isn't enough exposed by rel8. At the least, we'd need something equivalent to |
If you want to expose more, I think we'd be happy to accept a PR if it makes this work possible |
This closes circuithub#274 and circuithub#186, allowing the generation of CREATE TABLE statements from a TableSchema, as well as testing the table's schema in the database against the schema implied by the TableSchema type. Co-authored-by: David Kraeutmann <kane@kane.cx>
This closes circuithub#274 and circuithub#186, allowing the generation of CREATE TABLE statements from a TableSchema, as well as testing the table's schema in the database against the schema implied by the TableSchema type. Co-authored-by: David Kraeutmann <kane@kane.cx>
This closes circuithub#274 and circuithub#186, allowing the generation of CREATE TABLE statements from a TableSchema, as well as checking a TableSchema against a database to determine if the tables are defined correctly in the database to be read from/written to by rel8. It also adds tests for the creation and type checking of tables, to ensure they succeed/fail in appropriate cases. Co-authored-by: David Kraeutmann <kane@kane.cx>
I'd like to pretend I don't have a database at all because I don't understand SQL, and am hoping rel8 can give me the SQL necessary to create the db/table it will talk to. Is this possible given a
TableSchema
?The text was updated successfully, but these errors were encountered: