MySQL Forums
Forum List  »  InnoDB

Character sets and migration from 4.0 to 4.1
Posted by: James Day
Date: April 24, 2005 02:57PM

As the poster at sourceforge noted, the maximum row size is half the page size, so going just below 16k wouldn't be enough to make a record fit. You'd need to get just below 8k.

max_allowed_packet might be a factor if it's much lower than the usual one megabyte but it seems most likely that you're encountering the effect of a change to the character set handling between MySQL 4.0 and 4.1.

Before 4.1 the length of a char or varchar field specified the number of bytes it was to hold. As of 4.1 the length is the number of characters the field is to hold. The number of bytes required can be two or three times that in 4.0, depending on the character set in use. Possible solutions include using CHAR BINARY or VARCHAR BINARY or specifying the same character set you were getting by default in version 4.0. A read of the extensive new coverage of character sets in the manual will probably be helpful to you.

The normal database page size for InnoDB remains at 16k.

Options: ReplyQuote

Written By
Character sets and migration from 4.0 to 4.1
April 24, 2005 02:57PM

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.