Okie, i will also try this, as we also load data from a flat file.
regards
anandkl
On 8/31/07, Harald Vajkonny <[EMAIL PROTECTED]> wrote:
>
> Hi Ananda,
>
> Ananda Kumar schrieb:
> >
> > So you set the collation_database=utf8_bin, what was your
> > character_set_database values.
> character_set_
Hi Ananda,
Ananda Kumar schrieb:
>
> So you set the collation_database=utf8_bin, what was your
> character_set_database values.
character_set_database is "utf8". The collation utf8_bin slows down
queries, but is necessary in dealing with multilingual information.
utf8_general_ci is faster, but can
Hi Harald,
So you set the
collation_database=utf8_bin, what was your character_set_database values.
regards
anandkl
On 8/30/07, Harald Vajkonny <[EMAIL PROTECTED]> wrote:
>
> Harald Vajkonny schrieb:
> > In doing this I got another idea: Does anybody know the difference
> > between the collatio
Harald Vajkonny schrieb:
> In doing this I got another idea: Does anybody know the difference
> between the collations utf8_general_ci, utf8_unicode_ci and utf8_bin?
> I'll try these first and then get back to you about the results.
>
That was it. If I choose utf8_bin as collation everything wor
Dušan Pavlica schrieb:
> What's the charset and collation of your primary field in the table?
With which command do I get the charset and collation information of a
single field in a table? SHOW CREATE TABLE returns:
...
) ENGINE=MyISAM DEFAULT CHARSET=utf8 |
But I believe it is utf8, because when
Harald Vajkonny napsal(a):
Dušan Pavlica schrieb:
Try to convert file to latin1, if it's possible, create database with
latin1 charset, create table with required structure (you can set utf8
charset to string fields ) and then load data.
I can not convert the file into latin1, because
Dušan Pavlica schrieb:
> Try to convert file to latin1, if it's possible, create database with
> latin1 charset, create table with required structure (you can set utf8
> charset to string fields ) and then load data.
I can not convert the file into latin1, because it is multilingual (i.e.
Europea
Ananda Kumar schrieb:
> strange. did u exit and reconnect and did the select?
>
Yes, I tried it once more. I have to put the USE command before I change
session settings to "latin" to make it work without error (otherwise I
still get the duplicate message). But even after exiting I get the
natio
Harald Vajkonny napsal(a):
Ananda Kumar schrieb:
strange. did u exit and reconnect and did the select?
Yes, I tried it once more. I have to put the USE command before I change
session settings to "latin" to make it work without error (otherwise I
still get the duplicate message). Bu
Ananda Kumar schrieb:
> strange. did u exit and reconnect and did the select?
>
Yes, I tried it once more. I have to put the USE command before I change
session settings to "latin" to make it work without error (otherwise I
still get the duplicate message). But even after exiting I get the
nati
strange. did u exit and reconnect and did the select?
On 8/30/07, Harald Vajkonny <[EMAIL PROTECTED]> wrote:
>
> Ananda Kumar schrieb:
> > I used the latin collation and latin db character set, to load data
> > similar to you, and we got this done correctly.
> >
> > If your inserting multi byte da
> Does anybody know how I restart my mysql-server with the correct
> character and collation settings, if this is the cause for my problem,
> or if there might be any other reason for it. My mysql version is
> 5.0.26-12, running on a Suse Linux 10.2.
>
Meanwhile I managed to change the server s
Ananda Kumar schrieb:
> I used the latin collation and latin db character set, to load data
> similar to you, and we got this done correctly.
>
> If your inserting multi byte data, then u need to set the above
> parameters. This was one of the solutions give by mysql, i am not able
> to get the u
I used the latin collation and latin db character set, to load data similar
to you, and we got this done correctly.
If your inserting multi byte data, then u need to set the above parameters.
This was one of the solutions give by mysql, i am not able to get the url. I
will search my notes and get
Edward Kay napsal(a):
I would like to import data from a utf8-coded comma seperated file. I
created my database with "DEFAULT CHARACTER SET utf8 COLLATE
utf8_general_ci" and I started my mysql-client with the
--default-character-set=utf8 option. Nevertheless, when I input primary
key fields, whic
Edward Kay schrieb:
> Try using the SET NAMES 'utf8' statement [1] to tell MySQL that your client
> is sending data in UTF-8. I believe that as your server is latin1, it will
> assume this is the character set used by the command line client.
>
> [1] http://dev.mysql.com/doc/refman/5.0/en/charset-c
> I would like to import data from a utf8-coded comma seperated file. I
> created my database with "DEFAULT CHARACTER SET utf8 COLLATE
> utf8_general_ci" and I started my mysql-client with the
> --default-character-set=utf8 option. Nevertheless, when I input primary
> key fields, which differ only
Ananda Kumar schrieb:
> Before you import at the mysql prompt set below variables and then try
> again to load
>
> set session max_error_count=50;
> set session collation_database=latin1_swedish_ci;
> set session character_set_database=latin1;
This is not what I need, because I use utf8 as we
Before you import at the mysql prompt set below variables and then try again
to load
set session max_error_count=50;
set session collation_database=latin1_swedish_ci;
set session character_set_database=latin1;
regards
anandkl
On 8/30/07, Harald Vajkonny <[EMAIL PROTECTED]> wrote:
>
> Hello,
Hello,
I would like to import data from a utf8-coded comma seperated file. I
created my database with "DEFAULT CHARACTER SET utf8 COLLATE
utf8_general_ci" and I started my mysql-client with the
--default-character-set=utf8 option. Nevertheless, when I input primary
key fields, which differ only in
20 matches
Mail list logo
