Last modified: 2012-08-04 20:49:08 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T30133, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 28133 - "INTEGER UNSIGNED" is not a PostgreSQL data type
"INTEGER UNSIGNED" is not a PostgreSQL data type
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
FlaggedRevs (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: postgres
  Show dependency tree / graph
 
Reported: 2011-03-20 13:15 UTC by petter.tornberg
Modified: 2012-08-04 20:49 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description petter.tornberg 2011-03-20 13:15:51 UTC 
The extension does not work for PostgreSQL. The "INTEGER UNSIGNED" data type, which is widely used in FlaggedRevs.pg.sql, does not exist in (standard) PostgreSQL. 

Thus, installing and running "update.php" results in fatal database errors. 

(I could be more specific regarding OS, version and so on, but as far as I know, "INTEGER UNSIGNED" doesn't exist in any PostgreSQL version, independent of OS.)

Probably a good idea to actually test the extension on a PostgreSQL, rather than just fixing this thing.
Comment 1 Aaron Schulz 2011-03-20 14:49:59 UTC 
There aren't any unsigned ints used for PG in /trunk. The only straggler still in 1.17 was in a db patch file (not flaggedrevs.sql) and cleared out in r84365 (just before this report).
Comment 2 Aaron Schulz 2011-03-20 17:40:37 UTC 
I've backported some of the 1.17 (when these bogus definitions were removed) changes to 1.16.
Comment 3 Mark A. Hershberger 2011-03-22 05:44:31 UTC 
Aaron, looks like you've fixed the remaining issues, then?
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links