Last modified: 2010-05-15 15:48:32 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 T11700, 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 9700 - Page with Title contain U+25008 fail to create
Page with Title contain U+25008 fail to create
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.9.x
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
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: ---

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

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.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links