On Wednesday 21 December 2005 08:12, you wrote:
> Are you mean this problom only disposed in compile ?
yes and no...this way you tell mysql to use readline instead of libedit...so
the problem is (at least that was the problem for me) related to the lib
which is used for input processing...
> >
On Tuesday 20 December 2005 03:10, wangxu wrote:
> Are there two option?
> How to use them?
These are just two options which you will have to use when ./configure'ing the
source distribution
if you are using a binary distribution of mysql try downloading the source
distribution...
then rea
On Monday 24 October 2005 12:00, Bruce Martin wrote:
> Can you force it to keep the space by escaping the space?
> Something like:
>
> mysql> insert into test_strings set foo_1=' test\ ',foo_2=' test\
> ',foo_3=' test\
> ',foo_4=' test\ ';
no...doesn't work...guess i will have to use text :|
Kin
Hi!
I just hit something really strange which is either a bug in MySQL or a
dumbness bug of me.
I am trying to insert a string ending with a simple space and i really want
this space at the end of my string ;). Unfortunately MySQL kills this
whitespace when inserting into normal (var)char colu
On Wednesday 24 August 2005 20:01, MightyData wrote:
> What is the proper procedure to change the table (or database encoding)
> from latin1 to UTF-8 with MySQL 4.1.x? My thought is to export the data to
> text file, drop the table, recreate the table with the proper encoding and
> then import the
On Monday 09 May 2005 12:24, John Doe wrote:
> Am Montag, 9. Mai 2005 11.55 schrieb Andreas Steichardt:
> > Hi!
> >
> > We are storing UTF-8 data in out mysql database and we need to get the
> > length of the data. But length() doesn't return the number of chara
Hi!
We are storing UTF-8 data in out mysql database and we need to get the length
of the data. But length() doesn't return the number of characters but the
pure number of bytes.
SELECT LENGTH('köter') => 6
Currently we are doing something like that:
SELECT LENGTH(CONVERT('köter' USING 'ucs2')
Hi!
We are trying to migrate our applications to UTF-8 and so we started testing
the new features of MySQL 4.1 (still using 4.0 currently). But we are facing
some problems now. In our applications it could be theoretically the case
that there is arabic, hebrew, japanese and korean content in on
