Moodle

Character Set misreported on shared hosting

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Duplicate
  • Affects Version/s: 1.8.2
  • Fix Version/s: 1.6.6, 1.7.4, 1.8.4, 1.9, 2.0
  • Component/s: Database SQL/XMLDB
  • Labels:
    None
  • Environment:
    MySQL 5.0, PHP 5.1.6, Linux 2.6.22, Apache 1.3.37, HostMonster shared hosting
  • Database:
    MySQL
  • Affected Branches:
    MOODLE_18_STABLE
  • Fixed Branches:
    MOODLE_16_STABLE, MOODLE_17_STABLE, MOODLE_18_STABLE, MOODLE_19_STABLE, MOODLE_20_STABLE

Description

HostMonster's shared hosting MySQL database server does not change the GLOBAL variable for character_set_database relative to the current default database (Moodle's DB), but does change the LOCAL variable.

grep "SHOW VARIABLES LIKE 'character_set_database'" (should return three locations)

Change "SHOW VARIABLES" to "SHOW LOCAL VARIABLES"

Issue Links

This issue will be resolved by:
MDL-11743 install.php does not recognize UTF8 unicode setup and stops under DB Checker Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Eloy Lafuente (stronk7) added a comment -

Well,

I don't understand the GLOBAL / LOCAL (SESSION) distinction for the "character_set_database" setting.

Such setting isn't client/server dependent AFAIK, but the default encoding of the database where Moodle connects to. So, if one DB has 'utf8' as default encoding, the "character_set_database" should return 'utf8', no matter if asked GLOBALLY or LOCALLY.

Or, were am I wrong? How can we have different "character_set_database" settings depending of the GLOBAL/LOCAL thing?

Ciao

Show
Eloy Lafuente (stronk7) added a comment - Well, I don't understand the GLOBAL / LOCAL (SESSION) distinction for the "character_set_database" setting. Such setting isn't client/server dependent AFAIK, but the default encoding of the database where Moodle connects to. So, if one DB has 'utf8' as default encoding, the "character_set_database" should return 'utf8', no matter if asked GLOBALLY or LOCALLY. Or, were am I wrong? How can we have different "character_set_database" settings depending of the GLOBAL/LOCAL thing? Ciao
Hide
Permalink
Petr Škoda (skodak) added a comment -

Reading the docs and our code I also think we are not setting 'character_set_database' variable at all, we just require moodle database to be using unicode encoding. The easies solution is to drop and recreate the database with utf8 as default charset.

The problem with shared hosting is that everybody is disabling/limiting different "features" in PHP, MySQL or Apache. Majority of testing is done with default settings and default installations.

Show
Petr Škoda (skodak) added a comment - Reading the docs and our code I also think we are not setting 'character_set_database' variable at all, we just require moodle database to be using unicode encoding. The easies solution is to drop and recreate the database with utf8 as default charset. The problem with shared hosting is that everybody is disabling/limiting different "features" in PHP, MySQL or Apache. Majority of testing is done with default settings and default installations.
Hide
Permalink
Richard L. Enison added a comment -

PS,

There is already code in Moodle to perform the "easiest solution" of recreating the db as utf8; it reportedly doesn't work.

EL,

See Anthony Borrow's recent comments on MDL-11743.

RLE

Show
Richard L. Enison added a comment - PS, There is already code in Moodle to perform the "easiest solution" of recreating the db as utf8; it reportedly doesn't work. EL, See Anthony Borrow's recent comments on MDL-11743. RLE
Hide
Permalink
Eloy Lafuente (stronk7) added a comment -

This is closed as duplicate of MDL-11743 (fixed in CVS).

Ciao

Show
Eloy Lafuente (stronk7) added a comment - This is closed as duplicate of MDL-11743 (fixed in CVS). Ciao

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.