Skip to content
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

Dynamically created tables are "Classical" SQLAlchemy style unmapped #22

Open
gracebrownecodes opened this issue Sep 23, 2015 · 1 comment

Comments

@gracebrownecodes
Copy link
Contributor

See reference on SQLAlchemy mapping styles here. I made the switch from constructing class contents dictionaries and then using type to create the class (in "Declarative" style) to creating a "Classical" model class and building it up modularly a while ago, without realizing the difference. There is no problem with this, but I believe it might be confusing for beginning SQLAlchemy users, and would be easy to use the mapping API to create mapped model classes dynamically from the classical ones.

@gracebrownecodes
Copy link
Contributor Author

It seems that the mapping API is actually quite difficult. It turns out the Declarative style might be the way to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant