Last modified: 2010-05-15 15:42:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8323 - MySQL-specific GET_LOCK statement in FileStore.php
MySQL-specific GET_LOCK statement in FileStore.php
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.8.x
All Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-12-19 17:50 UTC by Gregory Foster
Modified: 2010-05-15 15:42 UTC (History)
0 users

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


Attachments

Description Gregory Foster 2006-12-19 17:50:39 UTC
MediaWiki 1.8.2 installation on PostgreSQL datastore.  Bug noticed when
attempting to delete all revisions of an uploaded file.

PostgreSQL error message:
[Tue Dec 19 11:09:28 2006] [error] [client 0.0.0.0] PHP Warning:  pg_query() [<a
href='function.pg-query'>function.pg-query</a>]: Query failed: ERROR:  function
get_lock(&quot;unknown&quot;, integer) does not exist\nHINT:  No function
matches the given name and argument types. You may need to add explicit type
casts. in ../mediawiki/includes/DatabasePostgres.php on line 381, referer:
http://www.website.us/w/index.php?title=Image:Catalert.png&image=Catalert.png&action=delete

SQL in function lock() in FileStore.php:38

Already recognized as a potential problem with an @fixme comment in the source.
Comment 1 Greg Sabino Mullane 2007-01-16 16:35:55 UTC
This has been fixed in r18582 (and thus is in 1.9): thanks for the report.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links