b) print *default_charset_info
$2 = {number = 8, primary_number = 0, binary_number = 0, state = 33,
csname = 0x8389ef0 "latin1", name = 0x8389ede "latin1_swedish_ci"
Current InnoDB-4.1 still does not support multiple charsets, but uses always
the default charset and collation
At 13:26 2002-03-13, Victoria Reznichenko wrote:
>Alex,
>Wednesday, March 13, 2002, 7:16:02 PM, you wrote:
>
>AK> I'm very much interested to know how do you manage multiple language
>support with
>AK> mySQL.
>
>AK> I haven't found how i can define different character sets for
>different tables
Alex,
Wednesday, March 13, 2002, 7:16:02 PM, you wrote:
AK> I'm very much interested to know how do you manage multiple language support with
AK> mySQL.
AK> I haven't found how i can define different character sets for different tables or
AK> even for separate databases.
AK> Do i have to run se
I'm very much interested to know how do you manage multiple language support with
mySQL.
I haven't found how i can define different character sets for different tables or
even for separate databases.
Do i have to run several mySQL servers, one per each charset?
Maybe, it is the solution for yo
I need to do some tests for a client involving japanese text. I've
recompiled the server with extra charsets = complex to have multi-byte
support.
I see how I can select the default charset upon startup. How can I
tell mysql that a particular set of tables (or the whole DB) should
use the japan
