This week, ten years ago, I was in London for MySQL AB‘s first “train the trainer” course, also meeting (for the first time) my first boss at MySQL Kaj. I’d been hired mid August as employee#25, also doing training but actually primarily as tech-writer for the MySQL documentation (taking over from Jeremy Cole, and essentially I was the documentation team for quite some time . So from this you can deduce that yes, I was hired without meeting either Kaj or anyone in-person! I don’t think we even had a phone call, only email. Oh the days

The training week itself was of course disrupted quite a bit by the events in New York. We had Jeremy who had come on a UA flight from the US, and others from all over the place… it also taught …

WikiLeaks Cable Offers New Insights into Oracle-Sun Deal (PC World)

Nothing too new or shocking in there, but the cable does offer some interesting insights.

My colleague Antoinette is hiring a MySQL Curriculum Developer. To raise awareness, here's her blog post again:

Looking to join Oracle’s MySQL team? Our training team is hiring a MySQL curriculum developer!

You can find the job description and apply here.

While the job description refers to Dublin as location, applicants can actually be based pretty much anywhere. Your curriculum development/design experience, database & MySQL expertise and proficiency in English will matter most than location.

If you have experience in designing and developing training courses, and are passionate about databases in general and MySQL in particular, we look forward to hearing from you!

My colleague Antoinette is hiring a MySQL Curriculum Developer. To raise awareness, here's her blog post again:

Looking to join Oracle’s MySQL team? Our training team is hiring a MySQL curriculum developer!

You can find the job description and apply here.

While the job description refers to Dublin as location, applicants can actually be based pretty much anywhere. Your curriculum development/design experience, database & MySQL expertise and proficiency in English will matter most than location.

If you have experience in designing and developing training courses, and are passionate about databases in general and MySQL in particular, we look forward to hearing from you!

The MySQL Documentation Team is looking for a senior technical writer. Main areas to cover are MySQL Workbench and MySQL Connectors. The position is for EMEA.

Candidates should be prepared to work intensively with our developers and support organization when writing documentation. Being a distributed team,  we meet mostly on IRC and coordinate our work through email and versioning systems such as Subversion. The base format we're using is DocBook XML, and we're not just writing but also processing and publishing all our documentation ourselves.

This means you should …

The MySQL Documentation Team is looking for a senior technical writer. Main areas to cover are MySQL Workbench and MySQL Connectors. The position is for EMEA.

Candidates should be prepared to work intensively with our developers and support organization when writing documentation. Being a distributed team,  we meet mostly on IRC and coordinate our work through email and versioning systems such as Subversion. The base format we're using is DocBook XML, and we're not just writing but also processing and publishing all our documentation ourselves.

This means you should …

I just answered in yet another bug report where user experiences problem because OS crash damaged InnoDB tablespace. I wonder why users don't use InnoDB recovery. Looks like I need to create an entry in Domas-style:

IF YOUR TABLESPACE

IS CORRUPTED

TRY

FORCING INNODB RECOVERY

http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

I got this question second time this week, so I think it is worth writing a blog post about this topic.
Question was "Why I get error in EVENT which calls a STORED PROCEDURE which already has HANDLER?"
This changed in version 5.5 after fix of Bug #36185, Bug #5889, Bug #9857 and Bug #23032. Explanation is in this commit:

 The problem was in the way warnings/errors during stored routine execution

      were handled. Prior to this patch the logic was as follows:      

        - when a warning/an error happens: if we're executing a stored routine,

          and there is a handler for that warning/error, remember the handler,

          ignore the warning/error and continue execution.      

        - after a stored routine instruction is executed: check for a remembered

          handler and activate one (if any).       …

I just answered in yet another bug report where user experiences problem because OS crash damaged InnoDB tablespace. I wonder why users don't use InnoDB recovery. Looks like I need to create an entry in Domas-style:

IF YOUR TABLESPACE

IS CORRUPTED

TRY

FORCING INNODB RECOVERY

http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

I got this question second time this week, so I think it is worth writing a blog post about this topic.
Question was "Why I get error in EVENT which calls a STORED PROCEDURE which already has HANDLER?"
This changed in version 5.5 after fix of Bug #36185, Bug #5889, Bug #9857 and Bug #23032. Explanation is in this commit:

 The problem was in the way warnings/errors during stored routine execution

      were handled. Prior to this patch the logic was as follows:      

        - when a warning/an error happens: if we're executing a stored routine,

          and there is a handler for that warning/error, remember the handler,

          ignore the warning/error and continue execution.      

        - after a stored routine instruction is executed: check for a remembered

          handler and activate one (if any).       …