E-Books for you

Unfortunately, MySQL versions prior to 4.1.2 assume that characters are always
eight bits (one byte), which poses some problems. To combat the issue when
installing extensions we have the ability to define different S???L files for servers, that
do and do not support UTF-8.
In MyS???L servers that do not support UTF-8, when we create fields, which define a
character length, we are actually defining the length in bytes. Therefore, if we try to
store UTF-8 characters that are longer than one byte, we may exceed the size of the
field. To combat this, we increase the length of fields to try to accommodate UTF-8
strings. For example, a varchar(20) field becomes a varchar(60) field. We triple
the size of fields because, although UTF-8 characters can be more than three bytes,
the majority of common characters are a maximum of three bytes.
This poses another issue, if we use a varchar(100) field, scaling it up for a
MyS???L server, which does not support UTF-8, we would have to define it as a
varchar(300) field.


Pages:
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75