Hi!
On Aug 14, 2008, at 12:17 PM, Ronald Bradford wrote:
There are plenty of instances where utf8 is not needed for VARCHARS
(e.g. website address, md5, zipcode etc), hence character sets at
column level are often used.
URL's could be UTF8 :)
This is one of the problems I see... people are trying to save a
little but then accidently shove junk from forms into their
applications.
A zipcode/MD5/UUID should be in a number or custom type.
The issue I see historically, is the internal memory usage in MySQL
of temporary tables for utf8 columns where it is defined then as a
fixed width. And I've seen plenty of schemas that are VARCHAR(255)
for all columns.
If the eBay Memory engine is introduced, a) do we use it for
internal temp tables, b) does it optimize for utf8?
We use the EBay engine so we are no longer limited to fixed length.
That does not solve all problems of size though.
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
