ncss-2014-group-3 / word-by-word

Group 3's word at a time social network

7 stars 4 forks source link

Change from sqlite3 to a better database #21

Open nhardy opened 10 years ago

sysr-q commented 10 years ago

4 deals with this.

Why Mongo? Why even NoSQL at all? The data that's being stored fits well into the relational database mindset.

nhardy commented 10 years ago

Just for the lulz. This 'issue' isn't really a serious one. Though, a more powerful relational database, capable of caching queries and concurrency might be of use. And if we're going for performance, some redundancy could be added to certain tables to lessen number of queries.

sysr-q commented 10 years ago

I've heard great things about PostgreSQL, but never used it myself personally, so I can't vouch. Definitely worth looking out for some external database though, even if it's just Oracle/MySQL/whatever-its-called-these-days. SQLite3 isn't that amazing.

nhardy commented 10 years ago

From what I've read PostgreSQL is very standards-compliant, so implementing it would be as simply as changing the database calls and not having to worry about changing SQL, while MySQL seems the de facto standard since it's mature and reasonably quick.

sysr-q commented 10 years ago

Renamed the issue since we'd probably want to stick with a relational database, right? Wouldn't be hard to move from sqlite3 to Postgres, really. Hardest part would be database migration, and even that's just a Python script away.

I'll do a feature branch moving to Postgres on the weekend if you're interested.

nhardy commented 10 years ago

Might have a some time on Sunday afternoon, but otherwise I'll be working.