Open ghost opened 6 years ago
Tbh i don't have much experience with relational databases, i tend to avoid them cause i'm more into NoSQL dbs, so it's up to you.
SQLAlchemy can do migrations, maybe it's worth taking a look at it for any db changes.
Alright, that's what I'll do then. Or maybe just add a new column in the unions
table, called members
. I don't see why we would need to use SQLa Migrate, wouldn't it be easier to just change the database manually since it's not deployed anywhere?
oh right yea, we can just remake the db !
IT would be trivial to do actually - SQLAlchemy provides interfaces for relationships. I can get to it.
Alright, nice, It's all yours!
Taking this off the milestone so we can get it closed and start a new one, in line with our deployment to PythonAnywhere.
That'd require a little restructuring of the database. I think the best way would be to remove the
union_id
field inusers
, and make a new table calledunion_connections
or something similar, which would contain two columns:user_id
andunion_id
. What do you think about this approach?