Oooh, that's a great idea! It would still require a potentially large amount of network traffic, but there's an additional benefit: if I specify the collation explicitly when I create the $sth, I can let MySQL handle any coercion between collations if the columns in the two tables do have different collations. Then there's a much better shot at getting consistent behavior.
In reply to Re^2: locales, encodings, collations, charsets... how can I match a given MySQL collation?
by xaprb
in thread locales, encodings, collations, charsets... how can I match a given MySQL collation?
by xaprb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |