[This has nothing to do with the financial crisis or the
McCain/FeyPalin ticket. Sorry.]
Last Wednesday began innocently enough. Philip's email to the
Falcon team, "Regarding Falcon Recovery", lamented the lack of
progress in fixing recovery bugs. He detailed specific failures
that he was seeing, many of them new, and pointed out that that
the number of recovery bugs was increasing. He closed with"All of
this means that the recovery problems must be tackled immediately
and head-on. A database without functioning recovery can be at
most alpha-quality software."He was, of course, absolutely right.
The lack of reliable database recovery is like flying with
non-locking landing gear, so we took a hard look at the
problem.
Then all hell broke loose.
Falcon Recovery …
The latest from the MySQL community
Ideas, releases, practical guides, and perspectives from the people building with MySQL.
Back on popular demand, Sebastian Bergmann will teach his 3-day
workshop Quality Assurance in PHP Projects in Australia
again! It's scheduled 8-10 December in Sydney.
Many applications using MySQL are written in PHP... this
three-day workshop will introduce/update PHP Developers to
writing unit tests for the backend and system tests for the
frontend of a web application as well as managing the quality
from development to deployment and maintainance using tools such
as PHPUnit,
Selenium
RC, phpUnderControl, PHP_CodeSniffer, and …
But users are human, and an unpredictable amount of unplanned
events can happen everywhere. When I was consulting, the above
cases were quite common.
Before MySQL 5.1, the only method to clean up the process list
was by hand, or using a cron job to do it from time to
time.
MySQL 5.1 …
I didn't really evaluate other issue tracking tools this time. I
know Eventum from my time at MySQL when it got acquired
from Joao Prado Maia. It's currently maintained by Bryan Alsdorf
(lordrashmi on Freenode IRC #eventum) who is very helpful. It
works well, it has a pretty decent user interface, I knew it
would do the job for OQ, and I got a local company (with Eventum
experience) to do the necessary customisation and integration
stuff.
So now any incoming general mail or form ends up there, which
properly removes me (and my inbox) as a communication bottleneck
for Open Query's effective growth. It also allows everybody
(including myself) to work more efficiently, since tasks have a
clear status and "owner" that is not dependent on email tagging,
flagging or location. Threads and issue can't just get lost - not
that they were, but it takes time, effort and brainpower to make …
|
|
|
Followers of my blogs and talks know that I am partial to the Federated engine. Not much as a normal way of storing data, but more as an auxiliary device to create innovative schemes. A few years ago I wrote an article, Federated: the missing manual where I listed most of the gotchas that you can meet when using the Federated engine. This article alone would be enough to discourage you from using Federated in production. If you attempt to use a Federated table like a normal one, your server will suffer, and possibly crash. |
Add the sad fact that …
Planned Falcon Blog posts: 4
Actual posts: 1
Team emails debating the cost of changing core components:
44
Post-debate emails suggesting a major change to a core component:
1
Days advance notice to change my LDAP password: 9
Nag emails to change my LDAP password: 9
Days of delay before changing my LDAP password: 9
Hours unable to access email after changing my LDAP password:
6
Calls to support after changing my LDAP password: 1
Falcon IRC non-system messages: 2022
IRC champ: Hakan (23%)
Runner-up: Vlad (21%)
Messages in German: 35
References to "Ramadan": 10
Best quote: "I try never to argue against clarity"
Source of quote: Ann
Intrusions by senior staff: 1
Number of times this week I typed a password into IRC: 1
Number of times this year: 3
|
|
The Large Synoptic Survey Telescope is making news once more. Its projected data inflow of 30 Terabyte per night has caught to the imagination of slashdot readers. Why is this interesting? Because it was not news to me. |
You may recall that I was enthusiast about a Astronomy, Petabytes, and MySQL at the MySQL
Users Conference 2008, and with reason. The engineers at Stanford
have a plan of storing petabytes of data into a cluster of MySQL
databases.
The technical …
MySQL, and thus currently Drizzle, logs stuff to it's error log.
"Stuff" being errors, warnings, and info messages. Inside the
code, they ultimately get sent to stderr, which is directed to
whatever file is specified by the "log-error" option. It's all in
the MySQL documentation at http://dev.mysql.com/doc/refman/6.0/en/error-log.html
I'm changing that in Drizzle, replacing the error logging stuff
with a plugin interface.
The first implementation will, just like the current builtin
system, write to a file, or to stderr. I expect soon after,
plugins that send the messages to syslog, as SNMP traps, and to a
CSV table, will be written.
Just like the query logging work, getting this going will shink
the drizzle core even more, and likely remove still more unneeded
locks.
There are relatively few markets that would benefit more from open source than home automation, with its myriads of different electrical nodes and associated complexity.
It is this opportunity that led to the creation of Marc Fleury and Mark Spencer's OpenRemote project, and that recently led them to release the Beehive database, ...
Well, I suppose its' true you can't use the official MySQL ALTER TABLE statement to do it, but if you're willing to trust your trigger coding abilities you can.All you need is an extra table and a couple triggers.The concept is fairly straight forward:Create a before insert trigger on the child table that validates the parent exists in the parent table.If there is no parent found, then insert a