Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 975289
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T03:33:46+00:00 2026-05-16T03:33:46+00:00

I’ve moved database from one host to another. I’ve used PMA to export and

  • 0

I’ve moved database from one host to another. I’ve used PMA to export and bigdump to import. The whole database have latin2 charset set everywhere where it’s possible. However in database, special chars (polish ąęłó, etc.) are broken. When I used SELECT i see “bushes” – “Ä�” insetad of “ą”. Then I’ve set document encoding to utf-8… And the characters are good. How to fix this? Can it be done using CONVERT in query? I don’t want to export/import database again, because it has over 200MB. What’s wrong?

Every PHP/MySQL query solution will save me.

Sorry if you can’t understand this, because I’m still learning english though.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T03:33:47+00:00Added an answer on May 16, 2026 at 3:33 am

    If a table contains the wrong kind of charset (let’s say utf-8 has slipped into latin1 column varhcar(255)):

    ALTER TABLE tablename MODIFY colummname BINARY(255);
    ALTER TABLE tablename MODIFY colummname VARCHAR(255) CHARSET utf8;
    ALTER TABLE tablename MODIFY colummname VARCHAR(255) CHARSET latin1;
    

    See also: http://dev.mysql.com/doc/refman/4.1/en/charset-conversion.html

    However, it is more likely you just have a wrong character set in your default connection. What does a SET NAMES latin1; before selecting result in?

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.