MySQL Forums
Forum List  »  InnoDB

Yet another mismatch (yet another solution)
Posted by: Gavin Stokes
Date: October 09, 2012 10:24PM

I discovered that the table that was giving me the problem had a hard-coded "utf8" character-set specification, while the referenced table had no character-set specification at all.

That was the entire problem in my case.



Edited 1 time(s). Last edit at 10/09/2012 10:24PM by Gavin Stokes.

Options: ReplyQuote


Subject
Views
Written By
Posted
648187
March 24, 2005 01:20PM
5370
October 09, 2012 09:48PM
3630
December 19, 2011 10:13PM
9084
May 09, 2006 06:01PM
8269
November 15, 2006 02:05PM
7310
T D
February 01, 2008 06:47AM
9118
August 27, 2008 08:08AM
9616
December 03, 2008 10:15AM
6096
May 01, 2009 07:39AM
3361
August 29, 2011 04:46PM
4929
s l
December 15, 2009 01:48PM
4860
December 22, 2009 02:54AM
3180
February 18, 2011 08:55AM
3770
May 24, 2011 10:11AM
Yet another mismatch (yet another solution)
3228
October 09, 2012 10:24PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.