Re:SparkFun's migration from MariaDB to PostgreSQL
by gnur on Wednesday November 13, 2013 @02:28AM
(#6723878)
As a hobby-projects-only developer, would there be any reason to switch from mariaBD to postgreSQL?
Scalability is no issue for me (I don't have to scale). And lately I hardly write any queries myself because of django..
[ Parent
| on HN ]
Re:SparkFun's migration from MariaDB to PostgreSQL
by andybak on Wednesday November 13, 2013 @03:59AM
(#6724111)
Yep. South is much happier with postgrSQL as it can do schema changes in a transaction and roll them back if there's a problem.
MySQL will just leave you with a half completed schema change which you'll have to fix by hand.
Re:SparkFun's migration from MariaDB to PostgreSQL
by gnur on Wednesday November 13, 2013 @06:55AM
(#6724624)
Ah good to know, doing my research also tells me Django 1.7 will include migrations out of the box with schema change transactions as well. Thanks!
Re:SparkFun's migration from MariaDB to PostgreSQL
by raverbashing on Wednesday November 13, 2013 @02:36AM
(#6723893)
For your case, especially using the Django ORM, no reason whatsoever.
Or, ok, there may be a reason, South used to not play so well with MySQL/MariaDB, this has improved over time but still may be a reason to use PostgreSQL
(Or just don't bother and use SQLite, depending on your case it may be just fine)
Re:SparkFun's migration from MariaDB to PostgreSQL
by collyw on Wednesday November 13, 2013 @05:57AM
(#6724420)
South still regularly complains at me for not using Postgress.
Re:SparkFun's migration from MariaDB to PostgreSQL
by raverbashing on Wednesday November 13, 2013 @09:30AM
(#6725334)
Yes, it complains, still, I'm not sure how much is truly "PostgreSQL is better" and how much is South not caring/not working around some issues.
Or even how much is limitations on the Python or Django DB drivers (two separate things)