This Thursday (May 28th, 14:00 UTC), Lars Thalmann will give a MySQL University session on MySQL Replication: Walk-through of the new 5.1 and 6.0 features. (This session was originally scheduled for May 7th, but had to be put off due to technical problems. Apologies.) Lars is leading the replication and backup teams at MySQL, so this is one of the best opportunities to ask whatever questions you might have about new replication features in MySQL.

For MySQL University sessions, point your browser to this page. You need a browser with a working Flash plugin. You may register for a Dimdim account, but you don't have to. (Dimdim is the …

It is getting summer in Germany: let’s have a PHP BBQ tour! The PHP BBQ tour is one week tour from Monday, 15.06. - Sunday, 21.06.2009 visiting the german PHP user groups. The tour will go through Munich, Frankfurt, Karlsruhe, Berlin, Dortmund, Hamburg and Kiel. The tour is an offering and a suggestion to the user group to come together for a barbecue instead of meeting in conference rooms in the middle of the summer, when the days are long. Everybody is invited to join me and other MySQLers on the tour to visit the PHP user group in his neighbor town.

It is getting summer in Germany: let’s have a PHP BBQ tour! The PHP BBQ tour is one week tour from Monday, 15.06. - Sunday, 21.06.2009 visiting the german PHP user groups. The tour will go through Munich, Frankfurt, Karlsruhe, Berlin, Dortmund, Hamburg and Kiel. The tour is an offering and a suggestion to the user group to come together for a barbecue instead of meeting in conference rooms in the middle of the summer, when the days are long. Everybody is invited to join me and other MySQLers on the tour to visit the PHP user group in his neighbor town.

I have been busy lately thanks to my internship project, which almost got screwed up. I was working in a team of 4 people, where we were building a web application, that was initially deployed at JBoss Server using JBoss Eclipse IDE (old version). Also, we had to interact with the centralized Oracle Server to setup our database for running the website.

Now, having being trained on some of those technologies in past few months, I thought it won’t be much of an issue. However, at the beginning of this month, I faced some weird issues which had no obvious answers. There weren’t any silly mistakes either. We were facing some issues with Oracle connectivity. I am not blaming Oracle or the company where we did the project. But, mix of old and new technologies, turned out to be quite confusing resulting in lot of trouble.

We were running out of time, so we decided to migrate our database to MySQL Server and use NetBeans 6.5 IDE, …

Last weekend I’ve reached a milestone in my work on the statistical index analysis for QOT. The code is available on Launchpad.

An example is worth a thousand words, so I start with one (once again I’m using employees-db):

$ ./qot –info –host=192.168.200.1 –analyse=possible –schema=employees –query=”select * from dept_emp where (dept_no = ‘d005′ or dept_no = ‘d006′) and (emp_no = 10010 or emp_no = 10011)”

/* Output produced by qot 0.1.6 GPL */
/*
Query: select * from dept_emp where (dept_no = ‘d005′ or dept_no = ‘d006′) and (emp_no = 10010 or emp_no = 10011)

selectivity:
all rows

used tables:
dept_emp (all rows)

ordering:
no ordering

related existing indexes:

…

A bug in libcurl affects how the heartbeat function of MySQL Enterprise Monitor works by sending it to an external website, often www.agent.com.

• Introduction
• The Problem with the Relational Database (Part 1 ) –The Deployment Model

I met with a friend of mine in New York recently who runs a credit card processing end-point company.  They specifically built their business around a non-relational database platform and feel they would have major issues had they chosen to build their business around a traditional …

A bug in libcurl affects how the heartbeat function of MySQL Enterprise Monitor works by sending it to an external website, often www.agent.com.

A bug in libcurl affects how the heartbeat function of MySQL Enterprise Monitor works by sending it to an external website, often www.agent.com.

I'm conflicted about the latest twist of the MySQL release saga, ie the announcement of the 6.0.11 alpha version and the accompanying note that it's the last 6.0 release and will be replaced by the already discussed milestone model. From an engineering point of view, I think this is the right step. I'm not sure about that, because I can't really tell exactly what is the engineering model chosen: trunk-first, then backport, or fix-in-releases, then forward port. I also can't tell whether the milestone model is going to be timeboxed or feature-scoped. Personally, I would prefer to see the former of both alternatives.

From a customer point of view, I'm even more confused, though much less concerned. Okay, so 6.0 won't become the marketing version number of any MySQL Enterprise release? Doesn't …