[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Re: Auto complete not working for authors



Hi Mathieu,

I hope you're not doing that upgrade tests on the production instance.

Have you done 'epadmin update/upgrade' thing?

What is your mysql version version, database charset and 
charset/collation of other tables?


###
If you'll you have to change encoding of your entire database some basic 
steps are:

1. dump database in utf8 (mysqldump with options default_character_set 
set-charset etc.) .. for current mysql, utf8 is default.
2. create new utf8 based database
3. import previously dumped data again with character set defined.

After step one you should verify character set of your dumped sql file. 
If it's latin1 iso-8859-1 .. you could use command line tools like iconv 
or recode to change file encoding and import data after that..

You could add/change character set and collations in dump file within 
'create table' statments..

The same applies if you are dealing with just one table not entire 
database, except you are not creating new database :)..

You can also find some useful hints here:
[1] http://kb.siteground.com/importexport_mysql_database/
[2] 
http://www.anchor.com.au/hosting/support/MySQL/Character_sets_and_Encodings
[3] http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html

Kind regards,
-- 
Alen Vodopijevec
Rudjer Boskovic Institute Library
lib.irb.hr/web/en | www.irb.hr


On 03/23/2015 07:39 PM, Mathieu Perron wrote:
> Well that didn't went too well,
>
> Here is the end of my message:
>
> SQL ERROR (execute): COLLATION 'utf8_general_ci' is not valid for
> CHARACTER SET 'latin1'
> DBD::mysql::st fetchrow_array failed: fetch() without execute() at
> /eprints3/cgi/users/lookup/name line 61.
> DBD::mysql::st execute failed: COLLATION 'utf8_general_ci' is not valid
> for CHARACTER SET 'latin1' at /eprints3/perl_lib/EPrints/Database.pm line
> 3211.
>
> How can I resolve these errors?  Do I have to change the default encoding
> for the database and then change the encoding for all columns.  I also
> realized that there are some columns set to latin1 and some to utf8 in the
> same table (e.g.: table eprint).  Is this ok?
>
> Thank you for your much appreciated help!
>
> Mathieu Perron
> IT Technician
> Biblioth?que Paul-?mile-Boulet
> Universit? du Qu?bec ? Chicoutimi
>
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/
>