Last modified: 2010-05-15 15:28:07 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 969 - save message: wrong delete statement
save message: wrong delete statement
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
1.3.x
PC Linux
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-12-01 11:36 UTC by Christoph Roeder
Modified: 2010-05-15 15:28 UTC (History)
0 users

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


Attachments

Description Christoph Roeder 2004-12-01 11:36:01 UTC
Hello,

when I save an message I got these SQL-Statement:

DELETE linkscc FROM linkscc,brokenlinks WHERE lcc_pageid=bl_from AND
bl_to='Anpassung'

Thanks
Comment 1 River Tarnell 2004-12-01 11:50:46 UTC
I may be missing something, but could you elaborate on where the bug is, please?
Comment 2 Brion Vibber 2004-12-01 11:54:23 UTC
There is probably an error message somewhere near that; can you 
please provide it?

Are you running on MySQL 3.x? If so, did you migrate from a MySQL 
4.x installation? Did you keep the configuration file from it? If so, 
try changing this line:

  $wgDBmysql4 = $wgEnablePersistentLC = true;

to this:

  $wgDBmysql4 = $wgEnablePersistentLC = false;

Does this resolve the issue?
Comment 3 Christoph Roeder 2004-12-01 12:22:35 UTC
thanks this solves the problem :)

PS: it's MySQL 3.23.49a-max, because it's not my own server

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


Navigation
Links