Rusty Razor Blade
I have never, ever seen this before. I don’t even know how the table was created with a different collation. However, I had all my other tables created with the character set utf8, no collation specified.
I had to convert the second table to match the character set. This probably wouldn’t have been a problem if I wasn’t joining on a character field.
alter table exclusion CONVERT TO CHARACTER SET utf8;
First time I’ve ever seen that one.
If you enjoyed this article, please consider sharing it!
I’ve found these kind of errors at column-level too, with these two collations general & unicode, it is a little weird…
Search the MySQL Reference Manual for “error 1267″, and you’ll be directed to this page:
http://dev.mysql.com/doc/refman/5.1/en/charset-repertoire.html
which explains what’s happening and why.
(Thanks to our brand new Google Appliance searching the MySQL Manual actually works now.
)
Regards,
-Stefan
Hi, I found your blog on this new directory of WordPress Blogs at blackhatbootcamp.com/listofwordpressblogs. I dont know how your blog came up, must have been a typo, i duno. Anyways, I just clicked it and here I am. Your blog looks good. Have a nice day. James.
Well spoken!! Thanks for information. Bookmarked!!!!
It has long been looking for this information, thank you.
#1146 – Table ‘XXXXX.XXXX.exclusion’ doesn’t exist
You save me and my prod environment ! Thank you so much !
Awesome! Really glad I could help.