Hi Jeremy, Thanks for the reply.
I think the problem is with the data itself. My Database table (with charset as utf8) contains "’" which I think is encoded improperly. Since I know the source of problem(Not using utf8 as encoding when using mysql gem), I could easily change the data (converting improerly encoded data like "’" to "’") to work with any of mysql (with encoding=utf8) & mysql2 gems. Can you please help me better understand what "encoding=utf8" does? Because I am thinking of using it, with mysql2 gem, just to be safe. Cheers, Satya On Saturday, March 24, 2018 at 4:26:24 PM UTC+5:30, Satyanarayana Gandham wrote: > > Hi, > > I am trying to migrate from using mysql gem to mysql2 gem because of some > DB transaction related issues. But, when I retrieve data from tables, I am > getting the data as "St. Michael’s Hopsital" instead of "St. Michael’s > Hopsital". When I am using mysql gem, I used force_encoding plugin with > 'UTF-8'. In DB, it is stored as "St. Michael’s Hopsital". > > Can you guys please help me solving this issue? > > Thanks, > Satya > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to sequel-talk+unsubscr...@googlegroups.com. To post to this group, send email to sequel-talk@googlegroups.com. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
