Project:Support desk/Sections/Database

__NEWSECTIONLINK__ = MediaWiki Database Support =

"Read database pages text - Wrong correspondency of text in the db with the one in the wiki"
Hello,

I can't find my the actual pages text in the database, i find but it isn't the actual version but an old version or not correct one. I correspond the last rev_text_id (of a page) in the table_revision with the table_text old_id but the text isn't the actual one (it's an old or a completely different). Did i made something wrong? Did i miss something? What can i do? I need to acces the pages actual text (all revisions if possible).

António antonioavf@gmail.com —213.138.228.242 23:54, 16 August 2008 (UTC)

SQL syntax error

 * MediaWiki version: 1.5.8
 * PHP version: 5.2.6
 * MySQL version: 5.0.51
 * URL: intra net- not available

I created a form from a module for Joomla called Chronoforms, Then I deleted the module without deleting the form. It seems like the form created overwrote a table in database... specifically to the data in the wiki data...and e somehow corrupted a table in the SQL...

How can I fix this issue....when try to open the wikisite i get the following 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 "MediaWikiBagOStuff:_doquery". MySQL returned error "1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '`��TV��@����ĴS���i�Vɽ�O�?�����g��!oj�C������2��>������/��پ���''�z��ͻ��?A�?'  at line 1 (localhost)".

luis (lucher100@hotmail.com)

—208.60.167.66 15:52, 3 September 2008 (UTC)

User permissions
I installed already the third version of MediaWiki according to the database I am the sysop and bureaucrat, my profile says I have the following rights Member of groups:	Users, Autoconfirmed users, Sysop, bureaucrat (User group rights)
 * MediaWiki version: 1.13.1
 * PHP version: 5.2.5
 * MySQL version: 5.0.62
 * URL: http://www.genealogy.henny-savenije.pe.kr/mediawiki/

Yet, I don't seem to have those rights, if I try to edit the Monobook css page

http://www.genealogy.henny-savenije.pe.kr/mediawiki/index.php?title=MediaWiki:Monobook.css&action=edit

You do not have permission to edit pages, for the following reason: This page provides interface text for the software, and is locked to prevent abuse. You can view and copy the source of this page:

If I search for users, there are none, yet according to the database there are three.

Can anybody help me more with this. I am at my wits end.

—Henny 13:07, 16 September 2008 (UTC)

latin1/binary …

 * MediaWiki - 1.13.1
 * PHP 	    - 5.2.6 (apache2handler)
 * MySQL     - 5.0.51b-community-nt
 * URL:      - Intranet use only

Hello,

I am a newbie at wiki's, so any additional explanations/link/docs will be more than welcome.

Here is my issue. I am trying to set up wiki as a intranet KB (Knowledge Base) tool. And before doing that, i am just testing what is what and which is which and how everything works. I managed to install the wiki and it works just fine. I am now going through the Backup procedures for a wiki, and going through the charset issues, quite frankly leaves me staring.

Not having that much experience, i chose the recommended option of binary charset. If i create the database myself, and set collation to Binary, i get an error when trying to run the installation script (i am running a WAMP server at home, for testing purposes, and will be doing the same on-location, i really don't need to bother on this aspect - or so i think. Database management is via PhpMyAdmin):

Creating tables...Query "CREATE TABLE `searchindex` ( si_page int unsigned NOT NULL, si_title varchar(255) NOT NULL default '', si_text mediumtext NOT NULL, UNIQUE KEY (si_page), FULLTEXT si_title (si_title), FULLTEXT si_text (si_text) ) ENGINE=MyISAM " failed with error code "Column 'si_title' cannot be part of FULLTEXT index (localhost)".

I don't change the options in the installation script, i pretty much leave them the way they are, just fill in the wiki name, the DB name, user and pwd.

If, however, i don't create the database myself, and let the script do it for me, it works like a charm. But i do notice that 2 of the tables are created with different storage engines, as opposed to InnoDB, the one i selected. (I am refering to searchindex and hitcounter). Also, their charset is different, as opposed to binary (the way i requested in the setup script). They are latin1_swedish_ci. I think these 2 exceptional tables are the source for the above error, so i should let the script create the database.

I started going through Manual:Backing up a wiki. And i found the note saying that:

'''In some common configurations of MySQL 4.1 and later, mysqldump can corrupt MediaWiki's stored text. If your database's character set is set to "latin1" rather than "UTF-8", mysqldump in 4.1+ will apply a character set conversion step which can corrupt text containing non-English characters as well as punctuation like "smart quotes" and long dashes used in English text.'''

Now, if i do a STATUS in the mysql console (after selecting the proper database), i get the following: mysql> status -- F:\wamp\bin\mysql\mysql5.0.51b\bin\mysql.exe Ver 14.12 Distrib 5.0.51b, for Win 32 (ia32)

Connection id:         386 Current database:      wspedia Current user:          ODBC@localhost SSL:                   Not in use Using delimiter:       ; Server version:        5.0.51b-community-nt MySQL Community Edition (GPL) Protocol version:      10 Connection:            localhost via TCP/IP Server characterset:   latin1 Db    characterset:    latin1 Client characterset:   latin1 Conn. characterset:    latin1 TCP port:              3306 Uptime:                1 hour 57 min 29 sec

Threads: 1 Questions: 10265  Slow queries: 0  Opens: 1032  Flush tables: 1  Ope n tables: 40 Queries per second avg: 1.456

What this is showing is latin1. But i selected binary, did i not?

If my understanding of the warning in the article is correct, then in my situation i should make sure to mention the charset in the dumping entry, to make sure my tables won't get converted to another charset right? To make sure they remain latin1 and i won't lose information.

Of course, several issues arise here. Or better yet, questions:


 * Why is it showing latin1 if i selected binary?
 * Considering the STATUS above, what will msqldump convert my database into when i dump? I have latin1, but what will it convert it into if i don't select --default-charater-set? Can i tell from this window?
 * Considering i select binary during installation, STATUS shows latin1, should --default-charater-set still say latin1 in the dump entry?

Can anyone please advise on this situation?

Thank you!

Alex - alex@hostingsolution.ro —Screwy 22:32, 20 September 2008 (UTC)