On the MySQL Proxy channel we get questions from time to time if the authentication can be intercepted and replaced data from a external source.

From now on, you can. For example if you want to get data from a external source (like LDAP) or want to implement roles.

Mapping Accounts to "Roles"

There isn't much needed to implement Roles for MySQL with the help of the MySQL Proxy.

• mysql.user doesn't contain users, but roles instead
• the proxy maps user-accounts to role-accounts with a script like above

It works like this:

1. login to the proxy

   $ mysql --user=jan --password=secret --port=4040
   

2. proxy looks up username password, finds a role for him

3. proxy replaces credentials ad hoc
4. mysql-server sees the role-name and role-password and lets the user in …

I presented on "Creating powerful web applications using GlassFish, MySQL and NetBeans/Eclipse" as the first talk of FISL 10 yesterday. The room was only partial full being the first talk of FISL but got packed towards the middle so that was exciting. The slides are available here.

The key message is that NetBeans and Eclipse provide a seamless development/deployment environment for GlassFish.

The several demos shown in the talk are explained at:

• …

I presented on "Creating powerful web applications using GlassFish, MySQL and NetBeans/Eclipse" as the first talk of FISL 10 yesterday. The room was only partial full being the first talk of FISL but got packed towards the middle so that was exciting. The slides are available here.

The key message is that NetBeans and Eclipse provide a seamless development/deployment environment for GlassFish.

The several demos shown in the talk are explained at:

• …

Yes, that's right, I mean *customers*. What do I mean with "MySQL Customer"? I would say "users who work for companies that prefer to buy products (tech support, subscriptions to enterprise binaries, short consulting engagements etc.)" instead of going for the familiar DIY approach.

Two years ago there was one and only MySQL product. There was the pluggable storage engine API, there was InnoDB outside the core development of the product and nothing else. Customers could confidently refer to a single provider, MySQL AB, to buy services and support from the creators of MySQL. Was it good for the customer? I would say yes, because the product was (and still is, of course) open source and there was a strong ecosystem and a wide adoption. But there was not much choice around: apart from relatively few strong but relatively companies, customers were in some way tied only to one provider.

Last year Sun acquired MySQL AB. I …

For some reason, the creation of a mapping to a database table poses a problem for certain people.

This is how it’s done in PDI 3.2.0 or later in the “Table Output” step:

Ogg video available over here

Until next time,
Matt

We've had problems with recordings lately, so the video streams (slides & audio) for these sessions were missing, or incomplete:

I'm happy to say that Dimdim (our conferencing system provider) was able to restore the files, so if you've missed either of those sessions, go ahead and look at the video stream!

…

You can download the MySQL database from the MySQL website http://www.mysql.com by clicking on the downloads tab. Scroll down to the MySQL database server & standard clients section and select the latest production release of MySQL, 5.1.35 at the time of writing.

Installation of MySQL Server

Unzip the setup file and execute the downloaded MSI file. Follow the instructions below exactly when installing MySQL Server:


Click on the "setup"




Perform a typical installation



…

Yesterday, I was invited to hold a presentation at the Berlin Open ‘09 Open Source event. This was related to earlier activities, such as the Open Source Yearbook published by professor Berndt Lutterbeck of the Technical University of Berlin. Professor Lutterbeck was also the main organiser behind Berlin Open.

After some, ehh, logistic challenges (a scenic detour over Alexandersplatz), I got to the Marshall House at Messe Berlin and met with the hosts. A well organised event, with lots of twitterings under http://twitter.com/berlinopen, and plenty of good …

This is just a brief announcement that the popular Open Source text editor control Scintilla, and the SciTe editor, which is a text editor based on Scintilla and part of the same project, these days properly supports MySQL Syntax.

Scintilla has supported generic SQL for quite a while, but this was heavily influenced by Oracle, and for example MySQL procedure code and folding didn't work properly. This has been fixed to an extent now, and there is a MySQL specific lexer that I contributed. This has been part of my own MyQuery tool since version 2.0, but that is a special version with the MySQL lexer patched in, but this patch is now included in the standard Scintilla and SciTe.

And just so you know, although my MyQuery tool is Windows only (yes, this is still the case), Scintilla and SciTe is not, they support Linux, GTK, Windows etc. So you can always use SciTe if …

If interested in contributing code to MySQL, you should attend the MySQL University session on contributing code to MySQL.

(Live broadcast with Q&A will be held on Thursday, June 25, 2009. You can still have access to rebroadcasts afterwards.)