Open yl3dy opened 8 years ago
Erm, could you clarify what's wrong with current MySQL setup? IMHO, one shouldn't try solving problems in application's architecture (e.g. just look at thread hotness calculation, that brutal crontab task) just by switching to a DBMS with more complex query optimization algos - DB schema and queries should optimized first. PostgreSQL is definitely better than MySQL but (IMHO, again) both of them are overkill here, I'm not aware about anything in this task that can't be done with pure ANSI SQL (and any DB engine that is compatible with it).
It isn't that MySQL is ruining the architecture (which is very bad regardless of used DBMS), but its treating of UTF-8, specially 4-byte symbols, is quite strange. MySQL was used because of legacy reasons, and it should be possible to replace with anything SQLAlchemy supports, but I haven't tried that yet. Anyways, it is a pretty much low priority task now as the current setup works somehow satisfactory.
Surely MySQL was a bad choice. See if PostgreSQL can be used as a drop-in replacement.