Re: 22001 Data too long for column
Posted by: Janos Hajdu
Date: August 18, 2006 10:32AM

I had a same problem.
First I worked with Latin2 default character set, and I made a dump. After it I changed tables default caharacter set to utf8 and I restore chema. In Query Browser I saw only: "Column Charset: Default".
But in the dump file I saw:

CREATE TABLE `forras` (
`azonosito` int(10) unsigned NOT NULL auto_increment,
`nev` varchar(45) character set latin2 collate latin2_hungarian_ci NOT NULL default '',
PRIMARY KEY (`azonosito`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

I changed it manually:

CREATE TABLE `forras` (
`azonosito` int(10) unsigned NOT NULL auto_increment,
`nev` varchar(45) character set utf8 NOT NULL default '',
PRIMARY KEY (`azonosito`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

and it works well!!
In Query Browser I see "Column charset utf8".

Options: ReplyQuote


Subject
Views
Written By
Posted
29342
October 30, 2005 11:16AM
12402
November 09, 2005 05:55AM
10145
November 11, 2005 07:12AM
10597
December 02, 2005 09:50PM
8217
January 02, 2006 03:43PM
6997
March 14, 2006 09:34PM
6552
August 23, 2006 06:24AM
6336
August 17, 2007 07:08AM
6478
March 13, 2008 10:29AM
12888
November 12, 2005 05:29PM
7527
June 09, 2006 03:39AM
9831
July 21, 2006 07:21AM
10157
November 15, 2005 01:01AM
Re: 22001 Data too long for column
6325
August 18, 2006 10:32AM
14181
March 12, 2006 10:59AM
5973
March 14, 2006 11:34PM
5866
February 13, 2007 04:57AM
5012
February 13, 2007 05:18AM
5631
October 09, 2007 02:56AM
5785
December 03, 2007 11:02AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.