Hi,
On Aug 14, 2008, at 3:22 PM, Brian Aker wrote:
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.
The Ebay memory engine is not used for internal temporary tables
currently. There are some technical limitations that prevent that
from being easy to do so. I hope to try to work on fixing those
limitations sometime to enable it.
As far as UTF8 with it go, when it is enabled, then varchar fields
that are stored variable width will take up only exactly what is
required.
Regards,
Harrison
--
Harrison C. Fisk, MySQL Staff Support Engineer
MySQL @ Sun Microsystems, Inc., http://www.sun.com/mysql/
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
