Show Mehdi GHEZALunread, Feb 27, 2010, 3:59:57 PM2/27/10 to doctrine-user Hello, I start with Doctrine 2 ALPHA 4 and try to save a record in a MYSQL $connectionOptions = array( My database tables use utf8_unicode_ci collation for text fields. I activate database log to watch query execute and Doctrine doesn't Where I'm wrong ? Thanks for your help :) Benjamin Eberleiunread, Feb 28, 2010, 5:28:29 AM2/28/10 to Mehdi GHEZALunread, Feb 28, 2010, 2:18:49 PM2/28/10 to doctrine-user Thank you for your help Benjamin. In Doctrine 2 ALPHA 4, Doctrine\DBAL\Event\Listeners\MysqlSessionInit For next peoples, here is a bootstrap example for Doctrine 2 in Zend use Doctrine\Common\ClassLoader, class Bootstrap extends Zend_Application_Bootstrap_Bootstrap $doctrineClassLoader = new ClassLoader('Doctrine'); $options = $this->getOption("doctrine"); $cache = new ArrayCache(); $em =
EntityManager::create($options['connection'],$config); Zend_Registry::set('EntityManager',$em); > http://www.doctrine-project.org/documentation/manual/2_0/en/dbal#data... Drakunread, Mar 30, 2010, 8:42:17 AM3/30/10 to doctrine-user Does this do so every SQL call or just once on establishing the connection? I havent yet discovered a way however to the generation of create echo $connection->getDatabasePlatform()->getCreateDatabaseSQL('mydatabase'); but I really need it to generate 'CREATE DATABASE mydatabase CHARACTER Regards, Drak This document describes how to convert your MySQL database from the latin1 charset to UTF8. Moodle requires that your Database is now UTF8 and will not upgrade if your database is not. For more information about UTF8 have a look at the doc on unicode. Why?You may see the following error when upgrading your Moodle. It is required that you store all your data in Unicode format (UTF-8). New installations must be performed into databases that have their default character set as Unicode. If you are upgrading, you should perform the UTF-8 migration process (see the Admin page). Default Mysql character setMoodle requires UTF8 in order to provide better multilingual support and has done since Moodle 1.8. However the UTF8 check during install and upgrade was only been implemented in Moodle 2.0 and you may find you are unable to upgrade because your database was not set up originally as utf8 when you first installed Mysql or because you have been running Moodle since before 1.8 and haven't previously converted your database. It is perhaps worth noting that Mysql is nothing to do specifically with Moodle. It is a database engine that is very widely used in open source projects and it contains details of all the stuff in your Moodle such as usernames etc and pointers to all the files that have been uploaded to it. You need to do two things. 1) Change your mysql to have utf8 as its character set and 2) Change your database to utf8. The descriptions elsewhere in this section cover making the utf8 database versions using mysqldump. To make mysql default to utf8 you can edit /etc/my.cnf as follows.
In the client section of my.cnf [client] ... .... ... default-character-set=utf8 ....
[mysqld] ... ... default-character-set=utf8 default-collation=utf8_unicode_ci character-set-server=utf8 collation-server=utf8_unicode_ci ... ... Having made your default character set utf, a mysqldump restore of your database with the --skip-character-set parameter, will restore the database with your new default character set of utf8. utf8_unicode and utf8_general are not the same but similar. The difference is described in the unicode documentation page. (Link below) Converting an empty databaseIf you have created your database schema and are receiving the error during your initial installation your Moodle database will still be empty. You can simply run the below query in your database to resolve the issue. Converting a database containing tablesIf you have previously installed Moodle and are now getting the error the following process will allow you to convert your database. Linux & Mac
%s/DEFAULT CHARACTER SET latin1/DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci/
%s/DEFAULT CHARSET=latin1/DEFAULT CHARSET=utf8/
wq
or alternatively using sed:
ExplainedThe following steps will guide you in creating a database dump, editing the database dump so that the correct charset and collation are used and then restoring the new database. To start please open a new terminal and move to a temp directory.
The first step is of course to dump out the database and of course we will use mysqldump for this. We do however need to set several arguments in order to clean up the charsets and provide a dump that is not going to cause you any problems if you are moving this database to a different database server or find yourself having to restore on a reverted system. usernameThe username to access your database.passwordThe password for the above user.-cComplete inserts for better compatibility.-eExtended inserts for better performance.--default-character-set=utf8To set the default character set. --single-transactionTo reduce our workload if anything goes wrong.--skip-set-charsetObviously not wanted or needed as we are changing it anyway.--add-drop-databaseRequired so we can restore over the top of our existing database.-BWe use this option so that our dump will contain drop table and create table syntax (which we will change the syntax for).dbnameThe name of the database to convert.When you run this command a database dump will be generated into dump.sql Next step is to copy dump.sql to dump-fixed.sql achieved by
%s/DEFAULT CHARACTER SET latin1/DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci/
%s/DEFAULT CHARSET=latin1/DEFAULT CHARSET=utf8/
wq
First we open the file using VIM, and then run the three commands. The first command replaces all instances of DEFAULT CHARACTER SET latin1 with DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci. This is used to fix up the database's default charset and collation. The second command replaces all instances of DEFAULT CHARSET=latin1 with DEFAULT CHARSET=utf8. This converts all tables from using latin1 to using UTF8. The third command simply saves it and exits.
WindowsThe following steps will let you create a database dump, edit it so that the correct charset (utf8) and collation (utf8_unicode_ci) are used, and then restore the new database. For this, you'll first have to download Super Sed (Win32 executable, zipped). Start by opening a command window and move to a temporary folder. [your mysql dir]\bin\mysqldump -u [username] -p[password] -c -e --default-character-set=utf8 --single-transaction --skip-set-charset --add-drop-database -B [dbname] -r dbdump.sql ssed -e "s/DEFAULT CHARACTER SET latin1/DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci/" dbdump.sql | ssed -e "s/DEFAULT CHARSET=latin1/DEFAULT CHARSET=utf8/" >dbdump_w.sql [your mysql dir]\bin\mysql -u [username] -p[password] [dbname] < dbdump_w.sql mysqldump parametersusernameUsername used to access your database.passwordPassword for the above user.-c (--complete-insert)Creates INSERT statements that include column names.-e (--extended-insert)Uses a multiple-row INSERT syntax that includes several VALUES lists; this results in a smaller dump file and speeds up inserts when the file is reloaded.--default-character-set=utf8Use and set utf8 as the default character set.--single-transactionThis option is useful only when using transactional tables such as InnoDB, as it helps minimize the locking time duration.--skip-set-charsetSuppress the SET NAMES statement (not needed because it is going to be changed).--add-drop-databaseAdds a DROP DATABASE statement before each CREATE DATABASE statement (to restore over the top of our existing database).--add-drop-tableAdds a DROP TABLE statement before each CREATE TABLE statement.-B (--databases)Defines the name of the database to convert.-r (--result-file)This option should be used on Windows to prevent newline “\n” characters from being converted to “\r\n” carriage return/newline sequences. The result file is created and its previous contents overwritten, even if an error occurs while generating the dump.Special chars won't import correctlyUnder certain circumstances, when restoring UTF8
encoded mysql dump, international special chars (you are able to correctly see using, say, vim editor), does not appears to be imported correctly. In such cases you may want to try the following under a *nix system: 1.login into mysql, 2.create a db with utf8 encoding and 3. import your dump using 'source':
That should do the trick. More information
|