Our Mac Developers have done an outstanding job in catching up with the Mac frontend. We have worked hard in the last days to get a little Christmas present out for all people waiting for a Mac Version of our Database Tool.
It’s a 1st alpha version, so don’t expect a full blown design application already - and the binary is Intel only this time (hey, it’s only Christmas folks ;).  But what we deliver is a working UI where you can load/save existing Workbench-documents and create diagrams from imported SQL-scripts. The canvas and the GRT system is up and running and there’s a shell which enables messing with the objects on GRT level. There are no object editors yet (so you can’t create and edit objects, but still build your diagrams for your existing SQL CREATE scripts) and wizards for exporting scripts, and connecting to databases are also missing. But enough writing, grab the .dmg package from our server and give it a try to get …

So we all know about the good old LAMP stack... Linux, Apache, MySQL, and PHP. It's a beautiful thing. I recently just started early development on a web application and instead of using Tomcat, Struts, Spring, Hibernate, or any of the Java-based frameworks that I am familiar with I've decided to take a step back to my programming past and use PHP with MySQL. Except this time, I'm using a Mac...

Let's start with my setup. I have a MacBook with OS X 10.5 (Leopard) so if you are running anything older this may not apply. Apache 2 and PHP 5 are shipped with 10.5 and I will talk about enabling them later.

The only piece we are missing is MySQL, and lucky us, they now make Mac binaries that you can find at www.mysql.com. Download the binary for the Mac (if you want to build the source get the tar.gz) and do the normal Mac install procedure. Once …

MySQL 5.1 reaches GA. But is it ready for production deployments? SpringSource launches commercial version of Apache Tomcat. BusinessWeek focuses on open source business models and open source in the downturn. And more.

Official announcements
MySQL 5.1 Downloads — Generally Available (GA) release for production use Sun Microsystems

SpringSource Launches tc Server; Continues to Redefine Application Server Market SpringSource

Open Solutions Alliance Appoints New President, Announces New Leadership Team Open Solutions Alliance

…

Previously on Log Buffer: Log Buffer #119.

And now.

Welcome to Log Buffer #120. My name is Warner, and I’m a SQL Server DBA at The Pythian Group. This is my first time on Log Buffer duties ever, so here’s hoping I can give everyone a fair and unbiased look at this week in the database blogging world (and related).

I admit I had no idea of the community or state of the PostgreSQL RDBMS, and so I definitely learned some new stuff this week. First off, over on “The Scale-out Blog” Robert Hodges invites us all to get our …

For the first time, MySQL includes Dtrace probes in the 6.0 release. On platforms that support Dtrace you can still find out a lot about what's happening, both in the Operating System kernel and in user processes, even without probes in the application. But carefully placed Dtrace probes inserted into the application code can give you a lot more information about what's going on, because they can be mapped to the application functionality. So far only a few probes have been included, but expect more to be added soon.

I decided to take the new probes for a spin. Oh, and rather than do it on a Solaris system, I figured I'd give it a shot on my Intel Core 2 Duo MacBook Pro, since MacOS X 10.5 (Leopard) supports Dtrace.

To begin with I pulled down and built MySQL 6.0.5 from Bit Keeper, thanks to some help from Brian Aker. …

For the first time, MySQL includes Dtrace probes in the 6.0 release. On platforms that support Dtrace you can still find out a lot about what's happening, both in the Operating System kernel and in user processes, even without probes in the application. But carefully placed Dtrace probes inserted into the application code can give you a lot more information about what's going on, because they can be mapped to the application functionality. So far only a few probes have been included, but expect more to be added soon.

I decided to take the new probes for a spin. Oh, and rather than do it on a Solaris system, I figured I'd give it a shot on my Intel Core 2 Duo MacBook Pro, since MacOS X 10.5 (Leopard) supports Dtrace.

To begin with I pulled down and built MySQL 6.0.5 from Bit Keeper, thanks to some help from Brian Aker. …

For the first time, MySQL includes Dtrace probes in the 6.0 release. On platforms that support Dtrace you can still find out a lot about what's happening, both in the Operating System kernel and in user processes, even without probes in the application. But carefully placed Dtrace probes inserted into the application code can give you a lot more information about what's going on, because they can be mapped to the application functionality. So far only a few probes have been included, but expect more to be added soon.

I decided to take the new probes for a spin. Oh, and rather than do it on a Solaris system, I figured I'd give it a shot on my Intel Core 2 Duo MacBook Pro, since MacOS X 10.5 (Leopard) supports Dtrace.

To begin with I pulled down and built MySQL 6.0.5 from Bit Keeper, thanks to some help from Brian Aker. …

I need to compile something and use the MySQL C++ library. I have mysql and mysql++ already compiled, I won’t go over how to do that now.

I added the following code to the top of my source:


#include <mysql++.h>


I got an error

/Users/jhaddad/dev/search_engine/main.cpp:4:21: error: mysql++.h: No such file or directory

Not cool.

How to fix:

In XCode, open up the project settings (under the project menu). Go down to search paths, and you can change your Header search paths to the correct locations where you installed whatever you’re looking for. In this case, mine was /usr/local/includes and /usr/local/mysql/

Next time you try to recompile, you’ll get a different error, this time it should be during Linking. Might look something like the below.

“mysqlpp::Query::store(mysqlpp::SQLQueryParms&)”, referenced from:

…