Category: MySQL


Back in December Diaof 2007, Andrew E. Bruno wrote an excellent article on how to use the open source program Dia to design databases.  He used the resultant design to create a MySQL database but the same principles could be used to create just about any relational database from the design.  Dia is available for Linux, *nix, and Windows.

Database Design with Dia

In this post I’m going to give a quick how-to on creating database schemas with a wonderful tool called Dia. I’ve often found having a nice visual representation of a database to be quite helpful but can’t stand keeping it up to date. As soon as you add a new column or change the design around you end up having to sync your visual diagram with your SQL files. It’s tedious having to manage the various SQL for building the database and this can be a larger pain when trying to support different database platforms each with their own SQL syntax. So before you create your next database read on and see how Dia can make your life a bit easier.

Dia is a program for creating diagrams and for this exercise we’ll be creating UML diagrams from within Dia. We’re also going to use a perl script called tedia2sql which will transform our Dia files directly to SQL for our target database. What’s also nice about creating database schemas this way is that you can generate SQL for multiple target databases without the maintenance overhead.

read more….

While the CakePHP framework is very good, the dbo “driver” (wrapper) between CakePHP and the PHP Sybase/Microsoft drivers ar not implemented to be actually usable.  Most of the issues are differences of SQL dialect between MySQL and the commercial DBMSs.

The issues tend to be simple ones such as, “select * from my_table limit 10″ to retrieve the first 10 rows not working.  Using “select top 10 col1,col2,….coln from my_table” will.

So how can you help?  Very easily! :)   The CakePHP website shows us how:

Contributing to Cake

We are always looking for contributions, so don’t be shy. There are two ways to get involved:

1. Documentation:

The Cookbook is ready to accept your input. Everyone can help with the documentation effort by simply logging in with your Bakery account, writing (or editing) a section and submitting it for review. The application is still under development, so if you find a problem, submit a ticket following the recommended procedure. Visit #cakephp-docs on irc.freenode.net.

2. Bugs, Enhancements and Optimizations:

Contributing code to CakePHP is easy: Submit test cases and attach them to tickets. That’s it. Fame, glory, and praise to all those who make the effort.

Thanks to all those who have already contributed to CakePHP. We look forward to everyone’s future contributions.

Take a look at the source code for the drivers.

Adrian Bridgwater

Adrian Bridgwater

Migration migraines: the top seven DBA data headaches

Posted by Adrian Bridgwater

Once or twice a year I get to work with an excellent DBA pal from Illinois called Jason Froebe who describes himself as a, “Perlmonger capable of speaking fluent munchkin.” His personal blog is called Ramblings of a Geek, but I keep telling him he should rename it “Froebe’s Frontal Lobe”.

read more at ZDnet…

The work that Adrian mentions is a last minute article for the International Sybase User’s Group that I wrote and he edited.  The benchmarking article that many people are waiting for is being held up by several groups giving their approval for the release of the material.

As always, it is a real pleasure to work with Adrian :)

The latest craze from software vendors to companies is to charge for each and every core a machine has regardless of whether or not you’re going to use it.

Get this, if you want to buy a production license for your database/middleware/web server, the vendor (starts with an “S”) wants you to send them the hardware specs of the box.  If you tell them it is a Dell superduper server with 8 quad core CPUs and 96GBytes of RAM but you only will be using a single core for the database and devoting the rest to the middleware/webserver, you STILL have to pay the vendor for all 32 cores (8 CPUs X 4 cores).  Your software license costs is now 32 times MORE what you should have to pay IMHO.

Lots of software companies are now doing this anti-customer practice just to beef up their short term revenues.

What makes them think that you won’t go to another vendor?

  1. Their competitors are probably doing the same sales tactic
  2. They have you by the family jewels, vendor lock in, and it will cost you far too much $$$ to migrate
  3. They think that you’re too stupid and/or timid to call their bluff
  4. FUD that is spread by well meaning and well known folk that don’t know jack about the open source alternatives

Who the hell do they think they are?

In his ZDnet blog, Adrian Bridgwater mentions my blog and the latest article I wrote for the ISUG Technical Journal.  This has totally made my month!  (Not counting the blue raspberry slushee zombie baby ;-)

Perl in the shell

Posted by Adrian Bridgwater

Adrian Bridgwater

Adrian Bridgwater

Why doesn’t anyone talk about computer programming languages these days? I’ve just spent the last couple of days working with a great guy called Jason Froebe on a Perl tutorial that really digs deep into making sure developers know that it is a fully-featured language and yet – all I see on the IT news-o-meter is corporate shenanigans not exactly likely to set the average software engineer’s world on fire.

read more…