Thursday, November 20, 2014
I assume you have created a "dump" of the data from production and copied it to your local MySQL version.
Also I assume you are comparing the same records on dev & production ("comparing apples to apples")
Check the character set (also known as "encoding") and collation settings on the table (on both your dev and production database) to make sure they are the same.
see http://dev.mysql.com/doc/refman/5.0/en/charset-table.html for an explanation
Note that these are set on a table-by-table basis. Because MySQL was originally invented in Sweden, the historical default for the character encoding is utf8_sweedish_ci. Typically people change that to utf8_unicode_ci
Once you verify they are identical on both machines, if you want to fix them on Production you'll want to use a Rails migration.
see also...
-Jason
On Nov 20, 2014, at 9:39 AM, Vladimir Gordeev <gordeev.vladimir.v@gmail.com> wrote:
but i don"t understand why it worked normally on my local computer and coming from the same databseDear sir, how do you define "same"? They could contain same data with different encodings.--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAP1h_xeY2c0L4qMpP8t0zSvKrjsP2J4b0HXvYsZ5epJ7UZ7Csw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
----
Jason Fleetwood-Boldt
All material © Jason Fleetwood-Boldt 2014. Public conversations may be turned into blog posts (original poster information will be made anonymous). Email jason@datatravels.com with questions/concerns about this.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment