The latest from the MySQL community

Teknologföreningen (or TF for short) is the Swedish language student corporation at Helsinki University of Technology. That’s where I started my studies in 1981 at the Department of Physics, together with Mårten Mickos and Michael “Monty” Widenius.

TF has a tradition of each year publishing “ …

Late February 2002 at the recommendation of our then-advisor Florian Müller, I first met with Ingrid Vos at Cafe Glockenspiel in Munich. Right thereafter, her company Marketing Communications became MySQL’s German PR agency.

Ingrid and her Munich based team have accompanied MySQL AB — and specifically MySQL GmbH — now for over six years. It has been a fantastic ride together. She has introduced us to numerous German journalists, and fixed plenty of meetings for Mårten, myself and others. Always with efficiency, a positive attitude, a happy smile and a friendly Austrian touch.

Being acquired by Sun Microsystems means changes in how we …

So I took my concerns over prepared statements to the #postgresql IRC channel on freenode. I pointed out that I think there should be a way to get server side handling of placeholders in statements but without the additional overhead of a second round trip or the drawbacks of overly generic query plans due to not being able to use the parameters in the planning stage. Some people have noted that this feature is available in MSSQL. It also seems to be available in PostgreSQL in the form of PQexecParams and its even exposed in ext/pgsql, though it's only used for sequence reading in PDO_PGSQL. It would be really cool if it could be used when emulating prepared statements (probably with a PostgreSQL PDO …

In 2000, MySQL co-founder David Axmark first told me about having met with Eben Moglen. His descriptions of Eben were always filled with respect and admiration — respect for a person who can keep his integrity and views of how software law should shape the world, and admiration for Eben’s pragmatism and ability to make a difference in the real world.

Over the years since David’s first encounters, Eben and his later estabished Software Freedom Law Center have repeatedly …

My name is Ravi Krishnamurthy - I am the Chief Software Architect here at Kickfire. I’ll be blogging about our thoughts on database technologies for data warehousing. More specifically I’ll be talking about current challenges, directions going forward, and the simplifications for wider market deployments and other ideas.

Data Warehouse (DW) queries are known to be more complex, more demanding, and longer running than OLTP queries. Some of the distinctive features of these DW queries that produce these characteristics are:

1) Table scan: Most OLTP queries are point queries updating or inserting a few transactional data. Most DW queries on the other hand are reporting or business intelligence (BI) queries which typically touch large numbers of rows of data, often computed by sequential table scans over the large data sets.

2) Many/complex joins: Multiple tables with many joins in the …

Compared to SQL*Plus (Oracle's cmdline client) which can as I understand produce complete paginated reports, the 'mysql' tool has fairly simple output formatting. I'm not generally fussed about that, as there are perfectly good other tools do make snazzy reports with. Some very cross platform (like web based), output PDF, not a problem. You can even write your own quickly these days.

But the cmdline tool has its use. I always teach my students the basics of it, and insist that some exercises are done using this tool. Familiarity (which involves some practice) helps there. Why? If all else fails, you generally do have mysql available on a machine. It's not hindered by remote ssh logins, or anything else. And, of course, for quickly checking something. And that's where the proficiency helps again. So, normally, you get this type of ASCII table:

mysql> select "Hello, world!" AS foo;
 --------------- 
| foo           | …

Peter Zaitsev wrote an interesting item on front-end performance of a website.

I've always tried to look at the front-end from the user perspective, rather than purely technical. Once you weed out what's not really necessary for the user, and also deal with issues like "how important is it that this number is live", you generally look at a fairly different site already ;-)

Before my time at MySQL, I wrote a little gizmo called Measly Mouse which leads a modest but still active life. When reading on from here, please remember it was designed in 2001 and hasn't really been changed since.

Measly Mouse retrieves a page and deals with redirects, CSS and other …

This fellow is pretty amazing: http://beta.ivancover.com/wiki/index.php/Eee_PC_Internal_Upgrades. To the already tiny Eee PC, he added (internally!):

1. USB hub
   
2. GPS with antenna
   
3. Bluetooth
   
4. Card reader w/ additioal SSD
   
5. Power switch (10 dip) for switching all extra foo on/off
   
6. Wifi upgrade 802.11n
   
7. FM transmitter
   
8. Modem (admittedly there's design space for that)
   
9. Touch screen
   
10. Temperature sensor
    
11. Heatsink
    

That's pretty cool...

A bit of advice to anyone wanting to write an article on MySQL that includes setting up users: familiarize yourself with the concept of Least Privileges. That is, only grant those privileges absolutely necessary to do a job and nothing more. I just finished reading an article on how to set up RSyslog to log to a MySQL database. Halfway through the article is a listing showing the grant statement. I’ll share just the fun part:

grant ALL ON Syslog.* …

My first reaction when I see a “grant all” is to ask: why? Why does an application need every database privilege? Well, I finished the article, then went to the RSyslog web site and spent all of 4 minutes researching why the app needs so much privilege. As it turns out, it doesn’t. Right there in blank and white:

“It is sufficient to …