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

The database schema needs to be declared somehow #17

Open
matt-bernhardt opened this issue Nov 29, 2015 · 2 comments
Open

The database schema needs to be declared somehow #17

matt-bernhardt opened this issue Nov 29, 2015 · 2 comments
Assignees

Comments

@matt-bernhardt
Copy link
Owner

I'm not sure of the best way to store this, but the database schema assumed by the rest of the platform needs to be documented somehow. This could be a set of SQL scripts describing the table setup, or something else.

@matt-bernhardt
Copy link
Owner Author

So far I've added table definitions to the fixtures directory to facilitate testing, but this is very different than what's needed for initial setup.

@matt-bernhardt matt-bernhardt self-assigned this Dec 13, 2015
@matt-bernhardt
Copy link
Owner Author

Two links of note for this...

Setup scripts in Python2:
https://docs.python.org/2/distutils/setupscript.html

Migrations in distcontrib:
http://distcontrib-migrate.readthedocs.org/en/latest/

It may be that this question is one that will push me to adopt SQLAlchemy, because the maintenance of database schema is probably more than I want to tackle. OTOH, I'm concerned about how much the schema would end up changing if I turn over table design to an external package.

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

No branches or pull requests

1 participant