I keep seeing this posts by some of the manager types on planet MySQL about how they or some other guy is worrying about open source vendors not raking in billions or are not stealing billions of money out of peoples pockets that should not be playing on the stock market and things along those lines. While I do agree that its great to see open source software flourish .. actually let me clear that up, why do I even care if open source software flourishes? I care because I think open source software enables a different kind of growth for society, one that is shared, one that lowers barriers, one that I feel is more in tune with a world at peace.

Of course I want people that take part in this to be able to provide themselves and their families a decent life. But the fact of the matter is, these people do not need …

I keep seeing this posts by some of the manager types on planet MySQL about how they or some other guy is worrying about open source vendors not raking in billions or are not stealing billions of money out of peoples pockets that should not be playing on the stock market and things along those lines. While I do agree that its great to see open source software flourish .. actually let me clear that up, why do I even care if open source software flourishes? I care because I think open source software enables a different kind of growth for society, one that is shared, one that lowers barriers, one that I feel is more in tune with a world at peace.

Of course I want people that take part in this to be able to provide themselves and their families a decent life. But the fact of the matter is, these people do not need …

For those that have been using Planet MySQL to follow the progress of Drizzle, we now have our own Planet Drizzle.

You can also get a RSS feed directly from http://feeds.feedburner.com/drizzle

I have been asked twice this week what version of MySQL I would choose for a new project.
As with most questions in life the answer is: It Depends?

In general I would now recommend for a new project to select 5.1, and he is why.

1. If it’s a new project and your not managing existing applications with older versions then 5.1 is slated for General Availability (GA) at some imminent time. Having been at Release Candidate (RC) for quite some time (almost 1 year), many people, both internally and in the community are just waiting for Sun/MySQL to get this version out.
2. MySQL 5.0 is in maintenance mode, it’s now 3 years old. MySQL is placing (I’m assuming) resourcing energies to current and future releases.
3. If your looking at releasing a product in the next 3 months for example, you do not want to consider the testing and deployment of a new version (e.g. 5.1) in the next 6-9 months.
…

Tonight I provided a scope in Best Design Practices for MySQL Applications - Part A of just how much there is to consider with a successful application. I only scratched the surface in some detail, a topic one could easily write a book on, and definitely provide a number more presentations.

At 42SQL we follow the “Scale 2 Success” (tm) approach covering Architecture, Availability, Scalability and Accountability. With this we are able to clearly provide a strategy towards building successful scalable enterprise solutions. For more information on how we may be able to help your organization with any performance and scalability needs, please use the Contact Form.

You can find a copy of my slides for this presentation at …

GlassFish and MySQL bundle was released a while ago and I finally got a chance to try it out. Here are simple instructions to get you started:

1. Download GlassFish and MySQL co-bundle zip from here.
2. Install the bundle (detailed docs)
   1. Create a temp directory and unzip the contents of bundle there. The contents are:
      
      

      -rw-r--r--   1 arungupta  arungupta   239703 Mar 19 02:57 3RD-PARTY-LICENSE.txt …

This includes the end of support for all things PHP 4 as noted by seemingly everybody on php planet. But I also wanted to reminds people that the same is more or less happening in the MySQL world too. Did you know that active support for MySQL 4.x ended along with the year 2006? Did you even know that MySQL 5.0 active support is ending this year!?! Given MySQL 5.1 no show mentality, they might have to review this. Well there is of course extended support that extends MySQL 4.0 support until this year, MySQL 4.1 until the end of next year and MySQl 5.0 until the end of 2011.

This includes the end of support for all things PHP 4 as noted by seemingly everybody on php planet. But I also wanted to reminds people that the same is more or less happening in the MySQL world too. Did you know that active support for MySQL 4.x ended along with the year 2006? Did you even know that MySQL 5.0 active support is ending this year!?! Given MySQL 5.1 no show mentality, they might have to review this. Well there is of course extended support that extends MySQL 4.0 support until this year, MySQL 4.1 until the end of next year and MySQl 5.0 until the end of 2011.

I have my first SQL Server project lined up. So I am just interested in hearing some stories from the trenches form people that have been there already. How does PHP and SQL Server 2005 work out together? How do they work out together with *nix or Linux specifically? How do they work together with a Mac (since all the developers on the projects use Macs)? What are the limitations?

I heard some issues with NCHAR's when going through FreeTDS. Since this is a swiss client, we will of course have to make the application localized in German, Italien and French. What extensions are you using? Is PDO_DBLIB worth a look or should one better stick to ext/mssql? I do not envision I am going to do ueberfancy things. Well looking through the requirements we will have to read a PDF from the server. We will also make extensive use of FULLTEXT …

I have my first SQL Server project lined up. So I am just interested in hearing some stories from the trenches form people that have been there already. How does PHP and SQL Server 2005 work out together? How do they work out together with *nix or Linux specifically? How do they work together with a Mac (since all the developers on the projects use Macs)? What are the limitations?

I heard some issues with NCHAR's when going through FreeTDS. Since this is a swiss client, we will of course have to make the application localized in German, Italien and French. What extensions are you using? Is PDO_DBLIB worth a look or should one better stick to ext/mssql? I do not envision I am going to do ueberfancy things. Well looking through the requirements we will have to read a PDF from the server. We will also make extensive use of FULLTEXT …