On 02/25/2013 07:40 AM, Chad wrote:
On Mon, Feb 25, 2013 at 7:27 AM, Mark A. Hershberger mah@everybody.org wrote:
Getting Jenkins involved in testing isn't the (only) answer, though it would certainly help.
If developers who were interested in those databases could watch includes/db, that would help, as well.
The latter is the real problem here. We don't have any people who are dedicated to supporting these. People show up, say they want to work on supporting these, then disappear.
Covering all the non-mysql/sqlite we "support":
- DB2 has been unmaintained for ages, and personally I'm in favor
of dropping that one altogether.
- MSSQL would be nice to improve.
- Oracle support's not bad (maybe not perfect), freakolowsy would
know more.
- Postgres support needs major work. There's a lot of inconsistencies
between PG and the other backends (especially for install/upgrade). There *are* people here who care about PG.
-Chad
Yeah. Just wanted to point people to prior roundups on this topic -- see http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/56384 & https://www.mediawiki.org/wiki/Bug_management/Triage/Databases_20111102 for some people Mark could reach out to to ask for testing & development help, and for this summary of what needed doing as of November 2011:
How you can help MediaWiki administrators who don't use MySQL:
- Write tests or specs. Ben and DJ Bauch want to work on better unit
testing per https://bugzilla.wikimedia.org/show_bug.cgi?id=32118 (special page SQL queries), and could use specifications to test against. Improve https://www.mediawiki.org/wiki/Database_testing .
The question: what do we need to test more often to keep RDBMSes happy? https://www.mediawiki.org/wiki/Database_testing & https://www.mediawiki.org/wiki/New_installer/Test_plan Permissions, searching, schema setup, schema changes, quoting & identifiers, weird page names, transactions, import, dump, & interface coverage seem like the main culprits.
And I think we can mostly agree that MySQL/MariaDB (InnoDB & secondarily MyISAM), SQLite, and PostgreSQL are higher priority than SQL Server/SQL Server Express, Oracle, and DB2, although others might volunteer as maintainers and get some of that switched around. :-)
- Try to reproduce this installation failure on SQLite or PostgreSQL:
Now fixed.
- Fix "Database layer should automagically add GROUP BY columns on
backends that need them (postgres)" https://bugzilla.wikimedia.org/show_bug.cgi?id=26273 . This is a large project.
Still needs fixing.
- Make a meta-schema so that we no longer use tables.sql as a canonical
source. Chad and Max started in http://svn.wikimedia.org/viewvc/mediawiki/branches/abstract-schema/ . See https://www.mediawiki.org/wiki/Bug_management/Triage/Databases_20111102#Idea...: for more discussion. This is a large project.
Where's this branch now, if it's still useful?
Thanks for working on this, Mark!