Page MenuHomePhabricator

Add PostgreSQL support to Translate
Open, LowestPublic

Description

MediaWiki database access abstraction layer supports PostgreSQL. Translate does not support PostgreSQL currently because the database table definitions have not been adapted to PostgreSQL.

If the table definitions are adapted to PostgreSQL, some testing is needed to confirm that Translate uses the access abstraction layer correctly.

Another question is whether it is possible to get continuous integration support for testing Translate with PostgreSQL to avoid regressions.

I think that when T191231: RFC: Abstract schemas and schema changes lands, we will get PostgreSQL support for almost no effort.

Details

Reference
bz26422

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 11:15 PM
bzimport set Reference to bz26422.
bzimport added a subscriber: Unknown Object (MLST).

Translate is not supported for PostgreSQL as a MediaWiki backend. Please use MediaWiki with a MySQL backend. Patches to make it compatible with PostgreSQL will be accepted and can be attached to this issue.

No, it is not, because we have no intention to support any other DBMS than MySQL for Translate. The previous resolution remains, and reopening this issue is a waste of time. Please set it back to LATER unless you are adding a patch to add PostgreSQL support.

So why not label it as WONTFIX if there is no intention to support any other DBMS than MySQL?

What Siebrand means is that we are not going to fix the code ourselves or give support but we of course accept patches if provided. This is an enhancement request and thus should stay open though.

karun.84 wrote:

I dont think this should block bug 384, as its an extension and its an enhancement as stated in the comments.

Closing this was WONTFIX. There are no plans whatsoever to get this done.

(In reply to comment #3)

No, it is not, because we have no intention to support any other DBMS than
MySQL for Translate. The previous resolution remains, and reopening this
issue
is a waste of time. Please set it back to LATER unless you are adding a patch
to add PostgreSQL support.

(In reply to comment #7)

Closing this was WONTFIX. There are no plans whatsoever to get this done.

Siebrand, this is not what WONTFIX means on this bugzilla. LATER is no longer available so "Lowest enhancement" has to be used in its stead, it was decided on wikitech-l.
I'm also setting nobody as assignee so that it's clearer, I think this will be enough to say what you want.

(In reply to comment #8)

I'm also setting nobody as assignee so that it's clearer, I think this will
be enough to say what you want.

No, it isn't. I don't want enhancement requests that will never be addressed clogging my bug triages. It's WONTFIX per description "The problem described is a bug which will never be fixed.", or in other words "PostgreSQL is out of scope for this MediaWiki extensions".

(In reply to comment #9)

I don't want enhancement requests that will never be addressed

Apart from whether it's WONTFIX or not, you could exclude lowest priority enhancements from your query.

ben wrote:

Hi,

We are considering patching rather than trying to export and re-import a postgres based wiki to MySQL. Although we changed all the tables, there is clearly some code we will also need to update.

For example :

Database error
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function ‘MessageGroups::loadGroupDefinitions.’ Database returned error ‘42803: ERROR: column "page.page_id" must appear in the GROUP BY clause or be used in an aggregate function LINE 1: ...CT /* MessageGroups::loadGroupDefinitions Ben */ page_id,pa... ^ .’

I suspect this will take some time - can anyone advise how we can replace the (SQL query hidden) message with the actual query (this is a private wiki at the moment)

cheers

Ben

(In reply to comment #11)

can anyone advise how we can replace the
(SQL query hidden) message with the actual query

See https://www.mediawiki.org/wiki/Manual:How_to_debug#SQL_errors

$wgShowSQLErrors = true;

Though you don't really need it because you can just have a look at MessageGroups::loadGroupDefinitions. Patches welcome.

Change 98045 had a related patch set uploaded by Lethosor:
Add PostgreSQL compatibility to Translate extension

https://gerrit.wikimedia.org/r/98045

Change 98045 abandoned by Lethosor:
Add PostgreSQL compatibility to Translate extension

Reason:
Stale

https://gerrit.wikimedia.org/r/98045

Nikerabbit renamed this task from Special:Translate does not support PostgreSQL to Translate does not support PostgreSQL.Jul 21 2015, 8:03 PM
Nikerabbit set Security to None.
Nikerabbit renamed this task from Translate does not support PostgreSQL to Add PostgreSQL support to Translate.Jul 22 2019, 8:59 AM
Nikerabbit updated the task description. (Show Details)
Nikerabbit removed a subscriber: wikibugs-l-list.

With the Abstract Schema mostly everything should work, except maybe some special queries.