Every once in a while the Continuous Integration reminds me that the code I write isn't "that" portable. I develop on Linux, push to the SCM and the CI goes out and builds on several Unixes and Windows.
Fixing windows build issues through the CI takes quite a while ...more ...
Roland opened a bug "Documentation indicates some MYSQL_FIELD->flags are deprecated which aren't."
The MySQL protocol uses the string values of
SET-fields. To indicate that this string
originated from a ENUM- or SET-column the
SET_FLAG are used
in the Column Defintion
Same as Roland ...more ...
forge.mysql.com is shutdown the protocol documentation found a new/old home at:
It documents the early days of
MySQL 3.20 as seen in:
up to the features ...more ...
We are proud to announce the release of
MySQL Proxy 0.8.3 (alpha)
which updates MySQL Proxy for the protocol changes introduced in MySQL 5.5 and 5.6.
All users of MySQL Proxy 0.8.x are recommend to upgrade.
Today a little history lesson.
I was on a quest to find the origin of this line in include/mysql_com.h:
#define CLIENT_LONG_PASSWORD 1 /* new more secure passwords */
"new" ? "more secure" ?
CLIENT_* flags are used between client and server to negotiate what capabilities they support. It allows the server ...
I use MacOS X for most of my development work, but part of my job is writing apps that run on all major Unixes and Win32. Most of the time bugs and memleaks are "portable", meaning that they appear on all platforms in the same way and fixing them on ...more ...
I'm preparing the code for my MySQLConf 2010 session "MySQL Proxy meets: Memcache" where I'll present how to replicate from MySQL to memcache by using the MySQL Proxy.
Part of it will be using the semi-sync replication support for MySQL 5.5 to implement a synchronous MySQL-to-Memcache replication ...more ...
http://programm.froscon.org/2009/track/OpenSQLCamp/index.de.html has all the sessions incl. my
MySQL Proxy: a MySQL toolbox Architecture and Concepts of misuse
It ...more ...