Replication channel failover is discussed in the MySQL manual and it is quite easy to implement. When the primary replication channel fails, all you need to do is some SQL queries, do a CHANGE MASTER TO, issue a START SLAVE and it should be replicating again. This fail-over procedure is also very useful if you are upgrading the Master MySQL Cluster mysqld processes doing binary logging. For this you do not need a (controlled) fail-over to the Slave Cluster.
Please update outdated and maybe false info about MySQL!
Today I have been updating the MySQL entry on the Python wiki. It wasn’t incorrect, but very, very outdated and gave a false impression about MySQL’s (or Sun’s..) DBMS. It is more inline with the PostgreSQL entry now, and I think also fair. Maybe the Firebird folks might update their wiki page too? This is a call to other projects out there. If you have a MySQL entry page in your wiki, please be sure to reflect the features that were added during the past years.
Running Python scripts within MySQL Workbench
In my previous blog post I explained how to enable Python in the MySQL Workbench GRT Shell. This blog explains how to run a simple Python script using Workbench. You don’t need to change any preferences to make this work. Save the following little script to a file called wbscript.py. It will print the tables in the first schema of the first model opened. import grtmodel = grt.root.wb.doc.physicalModels[0] for tab in model.
MySQL Workbench: Enabling Python in the GRT shell
Yesterday, 7 Oct 2009, MySQL Workbench 5.2.4-alpha was released. What interests me in particular is that Workbench 5.2 brings support for writing plugins using Python. Before it was only possible using LUA. Workbench comes with GRT (Generic RunTime) shell which allows you to access objects at runtime. It’s pretty neat, but how you enable it to use Python? Here is how: Open the Workbench Preferences dialog In the General section, set Interactive GRT Shell Language to Python.
Which Python versions should MySQL Connector/Python support?
Today we had a bug report that one of the tests failed. The as-keyword was used in exception handling, which is only supported since Python v2.6. Currently, MySQL Connector/Python should work with Python v2.4 and greater, but not Python v3.x. The Connector/Python README said we supported v2.3, but that’s not the case (anymore) since decorators are used, e.g. @classmethod. I’ll have to pull the trigger, but I think it’s safe to say that we’re only going to support Python v2.