As many of the Social Tools depend on each other, they should probably support Postgres at the same time...
- Mentioned In
- rEPGA5a463facfc62: Wrap date() calls to be inserted into the DB in Database#timestamp for optimal…
rENSUc4cb04fdb7e1: Wrap date() calls to be inserted into the DB in Database#timestamp for optimal…
rESPRd780f45681b1: Wrap date() calls to be inserted into the DB in Database#timestamp for optimal…
rEPGA55584cbdc339: PostgreSQL support
rENSUfa1285e935fd: PostgreSQL support
rESPR223dbd9b7733: PostgreSQL fix for the DB query in Special:UpdateEditCounts
- Mentioned Here
- T153012: Rename Comments database table to be in line with convention
You're welcome! :) Hopefully in the future we can say that "Social-Tools support all the DBMSes supported by MW core" (which is MySQL/MariaDB, SQLite and PostgreSQL currently) and it'll be an accurate statement; right now e.g. Comments' PG support is a bit buggy due to the stupid table name issue (T153012) and all the (unmerged) patches listed here need slight tweaking to add the OWNED BY bit to the sequences (see Anomie's comments on my Echo patch @ https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/Echo/+/565045/), but for now, I invite you to test these schemas out and try to break 'em!
Because while basic testing has been done and some issues have been fixed, I'm absolutely confident there are still some bugs when using social tools with a PG backend (as they were originally written for one DBMS -- MySQL -- only; SQLite as well as PGSQL support are literally afterthoughts instead of something that was a design consideration and thus a part of the development process).