ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Database Export through phpMyAdmin

June 18, 2012 9:35pm

Subscribe [1]
  • #1 / Jun 18, 2012 9:35pm

    counterintuity

    20 posts

    I had an experience where I had to roll back my database after failed upgrade.  After importing the backup database, I encountered the weird characters like “‚Äô” which suppose to be an apostrophe.  I later realized that the export’s collation was set to “latin1_swedish_ci” when I skimmed through the exported SQL file.  I had to use the EE’s Search and Replace for every weird characters.

    This puzzled me that I had to look at my other client’s database and try exporting the same way I did with the previous client.  I then saw the same thing.  I compared the exported SQL file and the live database (remember it has not been rolled back).  I found that the exported SQL has weird characters while the database doesn’t. (see attached image - example A and B)

    I looked into the tables’ setting and saw that all tables are set to “utf8_general_ci” except at the very bottom, you’ll find “latin1_swedish_ci”. (see another attached image)

    I also found that when I go to ‘Operations’ tab, the collation is set to “latin1_swedish_ci”.

    Do I have the setting wrong?

  • #2 / Jun 20, 2012 10:49am

    Dan Decker

    7338 posts

    Hi counterintuity,

    Thanks for your question!

    The most important thing is to be consistent and set the database and tables to all the same collation.

    ExpressionEngine 1.x is more lax in the type it allows or expects. However, ExpressionEngine 2 uses UTF-8 across the board. If you plan on upgrading, I would suggest you standardize on that now.

    Let me know if you have any other questions!

    Cheers,

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases