Dear MySQL Users,

We are proud to announce that we have reached the Beta 1 for MySQL Workbench 5.2. Beta 1 is “functionally complete” and shows the new features for the upcoming version of Workbench GUI product.

The team has worked very hard to reach the goal of including all our new features within this first public beta version. We know there is still a lot of fine tuning and stabilization to be done over the coming weeks to get it solid on all platforms, but this release marks an important milestone.  Your beta feedback is key to this.

MySQL Workbench 5.2 Beta 1 provides:

1. Data Modeling
2. Query (upgrade from MySQL Query Browser)
3. Admin (upgrade from MySQL Administrator)

If you are a current user of MySQL Query Browser or MySQL Administrator, we look forward to your feedback on all the new capabilities we are delivering in a single unified MySQL Workbench …

Join us for a free webinar tomorrow where we will present the fundamentals of migrating a sample application from Microsoft Access to a MySQL back end. We will be giving the presentation twice, at 14:00 Central for EMEA and 10:00 Pacific for North America. To register, visit here.

Today morning when I was trying to execute a peice of SQL code and all the time I was welcomed by the below error.

ERROR 1037 (HY001): Out of memory; restart server and try again (needed 123456789 bytes).

If we get this kind of error message then the first thing we need to check is the available memory on the server and have to ensure that the server has not run out of disk space for the swap file and also need confirm that there is enough free memory for MySQL to grow.

 This indicate that we need to increase or decrease the values of some buffers to manage memory usage more efficiently otherwise MySQL might complain about the same thing by means of above error message.7TKU66CE8V5W

Il reste encore quelques places pour cette matinée dédiée à l'optimisation des performances MySQL.

Date : 24 novembre 2009
Lieu : Centre de Conférences, Capital 8, 32 Monceau, 75008 Paris.
Accueil : 9h00 (petit déjeuner et café seront offerts).
Prix : Cette matinée est gratuite !

Session 1 : 9h30-10h45

• Architecture MySQL : Parsing, exécution, optimizer, query cache, binlog…etc
• Architecture Innodb : Clustered index, bufferpool, hash index, insert buffer, locking model, MVCC, recovery log, checkpoint…etc. Comparaison avec les autres moteurs de stockage (PBXT, MySQL Cluster) et bases de données (PostgreSQL, Oracle ..).

Pause/Café : 10h45-11h00.

Session 2 : 11h00-12h30

• Évolutions récentes : Google SMP …

So, we have been building up our code library at dealnews for 9 years. It was started at the end of PHP3 and the beginning of PHP4. So, we did not have autoloading, static functions, and all that jazz. Classes had lots of overhead in early PHP4 so we started down a pure procedural road in 2000. And for a long time, it was very maintainable. We had 2 or 3 developers for most of this time. We now have 5 or 6 depending on whether we have contractors. There are starting to be too many files and too many functions. We find ourselves adding new files when some new function is created instead of adding it to an existing file because we don't want to have huge files with 100 functions in them. File names and function names are getting longer and more ambiguous. For example, we have a file called url_functions.php. It contains functions to generate URLs for different types of pages on the site, functions to …

Hi all!

I’ve been reading through the requested features for the new client on the wiki here:

• Proposed Client Features
• BOOTS Console API Design

I think all the stuff on that link is excellent so far. I’d also like to request a feature that I think will be a really cool timesaver for DBAs and developers using Drizzle.

Macro Support

Remember, “way back when” you used Microsoft Excel and were able to start recording your actions, then when you stopped recording, Excel would store a “macro” of your actions that you could subsequently replay?

I think this would be incredibly useful for folks who do repetitive work in the console.

Sure, I know, I …

We are pleased to announce the availablity of the 0.9.5.1 alpha release of InfiniDB Community Edition.  This is our latest alpha release and is not recommended for production work. 

New functionality we’ve added with 0.9.5.1 includes:  

Support for union and union all. 
Support for 23 new distributed functions.   
Cleanup of system catalog reduces disk usage on new installs.
Support for GCC 4.4 and Ubuntu 9.10.

We are pleased to announce the availablity of the 0.9.5.1 alpha release of InfiniDB Community Edition.  This is our latest alpha release and is not recommended for production work. 

New functionality we’ve added with 0.9.5.1 includes:  

Support for union and union all. 
Support for 23 new distributed functions.   
Cleanup of system catalog reduces disk usage on new installs.
Support for GCC 4.4 and Ubuntu 9.10.

There are a lot of tutorial out there describing how to use PHP's classic MySQL extension to store and retrieve blobs. There are also many tutorials how to use PHP's MySQLi extension to use prepared statements to fight SQL injections in your web application. But there are no tutorials about using MySQLi with any blob data at all.

Until today... ;)

Preparing the database

Okay, first I need a table to store my blobs. In this example I'll store images in my database because images usually look better in a tutorial than some random raw data.

mysql> CREATE TABLE images (
       id INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
       image MEDIUMBLOB NOT NULL,
       PRIMARY KEY (id)
       );
Query OK, 0 rows affected (0.02 sec)

In general you don't want to store images in a relational database. But that's another discussion for …

Dear Community,

We are pleased to present the 20th build of MySQL server with Percona patches.

Comparing to the previous release it has following new features:

• The build is based on MySQL-5.0.87
• innodb_rw_lock.patch is ported from InnoDB Plugin 1.0.3
• To be compatible with RedHat RPM repository, the naming scheme has changed to

      <rpm name>-<mysql version>-<percona build version>.<buildnumber>.<redhat version>.<architecture>.rpm

  Example:

  MySQL-server-percona-5.0.87-b20.29.rhel5.x86_64.rpm

See release notes for earlier changes.

Since the build 20 MySQL server with Percona patches is available in …