Last modified: 2010-05-15 15:48:32 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 9700 - Page with Title contain U+25008 fail to create
Page with Title contain U+25008 fail to create
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-04-26 00:50 UTC by kentsin
Modified: 2010-05-15 15:48 UTC (History)
0 users

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


Description kentsin 2007-04-26 00:50:19 UTC
When try to create a page with title contain the char U+25008 either create it
directly or rename a existing page the following :

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 "Article::insertOn". MySQL returned error "1406: Data too
long for column 'page_title' at row 1 (localhost)".
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-04-26 01:09:54 UTC
What was the full page name that you tried to create?  U+25008 should take up
only four bytes by itself.
Comment 2 Antoine "hashar" Musso (WMF) 2007-04-26 17:24:56 UTC
I have been able to create a page with U+25008.
Marking bug as worksforme.
Comment 3 Brion Vibber 2007-04-26 19:18:56 UTC
You're using the experimental MySQL 4.1/5.0 UTF-8 schema, and thus are limited
to MySQL's incomplete UTF-8 support.

Use the default (compatible) schema, which actually works. :)

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