Better DB Schema

[softbobo]

Already now it becomes apparent, that the quickly constructed DB schema will not satisfy all our (future) needs. For example in #27 we state, that sending the location alongside the event was a nice feature. That makes a new table necessary. What is necessary to optimize our DB structure? I think:

• reconsidering our choices for the storage of dates and times
• putting constraints on text columns
• using an ORM - here SQLAlchemy is feasible, as mentioned elsewhere
• introducing a location table

Also, at the moment our DB is very thin and hasn't got a lot of realations going on. Yet we should at least discuss the possibility of using a different DBMS that might suit our future needs better.

The whole proposal is to be seen as part of a bigger milestone, probably 1.0.0

[obitech]

We should also look at enabling database migrations while we're at it

[softbobo]

I agree on database migrations. I think it is also advisable to think about an automated backup mechanism of our data. I know that SQLite has something like this built in but am not sure how this is implemented in SQLAlchemy, if at all.

[obitech]

I think it is also advisable to think about an automated backup mechanism of our data.

I agree. But that is probably more like an "operations problem" which we need to discuss in a different step/issue as it's independent of using SQLAlchemy.