In this discussion (with minor edits): http://www.mysqlperformanceblog.com/2010/01/21/when-should-you-store-serialized-objects-in-the-database/
I was discussing compression — it typically is better done on the application end. If you have 20 web servers for each DB server, you can spread the compression load to 20 servers rather than having one DB server do it. I had proposed years ago to Monty to have compressed columns and change the client-server API to recognize them such that the client lib would do the decompression. This would also mean less network traffic. And the server could do it if the client version was too old. So I put forth the suggestion to have compressed columns and integrate it at the client/server api level, especially with prepared statements. Steven Roussey Network54 Corp. _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
