MySQL AB today announced that Comsys, a specialist in interactive telephony solutions, has selected the MySQL Embedded Server to power its VOIP solutions. Comsys provides telecommunication products and hosted services in the converging arena of IN, 3G, SIP and VoIP networks for mobile and fixed line telephony operators, MVNOs and call centres. Comsys selected the MySQL open source platform in order to meet the very demanding availability requirements of the telecom space, and to deliver a high level of reliability combined with low operational costs.

MySQL 5.1 offers an extremely useful feature called information_schema plugins. This feature allows dynamic runtime loading of a shared library into the MySQL server to implement a table in the information_schema database. The SQL standard (ISO/IEC 9075-11:2003) allows database implementations to extend the information_schema. MySQL 5.1 transfers the possibility to do this directly to privileged database users so they can extend the information_schema themselves, in any way they see fit.

Last time, I introduced the notion of strict and lenient updates.  Now it’s time to see what the performance characteristics are of each.

Just to rehash, we are focusing on the storage engine (a la MySQL) level, and we are looking at a database on a single disk—the one we are using for illustration is the 1TB Hitachi Deskstar 7K1000.  It has a disk seek time 14ms and transfer rate of around 69MB/s [See tomshardware.com] We will insert and delete random pairs, each 8 bytes.  So that’s 62.5 billion pairs to fill the disk.

Strict Updates

These are the easier update types to analyze.  Please review the definition of strict updates from the last blog entry.  Now notice that each insertion or deletion requires a point query.  For example, during an insertion, in order to determine if there’s already a row with a particular key value in the database, one must look up that key.  In order …

In all versions we updated Apache to 2.2.8, PHP4 to 4.4.8 and phpMyAdmin to 2.11.4. The Linux and Mac OS X versions contain also updated Perl (5.10.0) and MySQL (5.0.51a) releases.

Get the downloads and more details on the specific platforms XAMPP project page.

mysqlcompiler

We recently integrated MySQL 5.0.45 version with Open Solaris. MySQL 5.0.45 is available in SXDE 01/08. Sun Studio was used to compile MySQL on both Solaris SPARC and Solaris AMD64 platform.

This blog entry describes the changes that were made to improve MySQL performance using Sun Studio:

• Enable function inlining when Sun Studio is used.
  • The header file univ.i has the following code:
    
    • #if !defined(GNUC) && !defined(WIN)
    • #undef UNIV_MUST_NOT_INLINE /* Remove compiler warning */
    • #define UNIV_MUST_NOT_INLINE
    • #endif
  •  Modifying it to add Sun Studio compiler as under:
    • #if !defined(GNUC) …

MySQL 5.0.45 is integrated with Open Solaris build 79. It is available in Solaris Express Developer Edition (SXDE) 01/08. MySQL 5.0.45 is integrated with Solaris Service Management Facility (SMF).

This blog entry describes the steps that were taken to integrate MySQL with SMF.

First a quick recap of what is SMF:

SMF is the core component of the predictive self-healing technology available in Solaris 10, which provides automatic recovery from software and hardware failures as well as adminstrative errors.
Some of the advantages of using SMF are as under:

• Failed services are automatically restarted in dependency order, whether they failed as the result of administrator error, software bug, or were affected by an uncorrectable hardware error.

• More information is available about misconfigured or misbehaving …

For the first couple of years after we created the opentaps Open Source ERP + CRM, we thought about our community as many other open source projects do. We defined our "community" as the sum of all the users, developers, and contributors of opentaps, and we asked ourselves questions like "What can we develop for our community?" and "How do we increase the size of our community?"

Only much later did I realize that this is completely wrong. It is wrong because an open source project is not an island, but rather part of a greater open source community that really comprises of all the open source projects out there. In that sense, there is no such thing as "our" community or "your" community. Instead we are all part of one open source community that is linked together and ultimately succeeds or fails together.

What has created this greater open source community is simply …

Thanks all for the help on getting my log_addpartition event running, dynamic SQL was just the ticket. 

I'm now focusing on writing the sister event: 'log_removepartition', which will find and purge partitions older than some time interval. The information schema comes in quite handy here, as I can query the PARTITIONS table to see all partitions.

read more

Last time, I introduced the notion of strict and lenient updates.  Now it’s time to see what the performance characteristics are of each.

Just to rehash, we are focusing on the storage engine (a la MySQL) level, and we are looking at a database on a single disk—the one we are using for illustration is the 1TB Hitachi Deskstar 7K1000.  It has a disk seek time 14ms and transfer rate of around 69MB/s [See tomshardware.com] We will insert and delete random pairs, each 8 bytes.  So that’s 62.5 billion pairs to fill the disk.

Strict Updates

These are the easier update types to analyze.  Please review the definition of strict updates from the last blog entry.  Now notice that each insertion or deletion requires a point query.  For example, during an insertion, in order to determine if there’s already a row with a particular key value in the database, one must look up that key.  In order …

I’m following what ezComponents doing for sometime now.
Quite nice framework for whatever you need.
I gave a try to write a mysql schema sync.
Real easy to write. only 4-5 lines of code to sync schemas.
It would have been great if it was actually working. The outout sql ddl is not runnable in some cases (syntax errors). Or the order of the columns are different.
I’m sure they’ll fix it soon but this tells me they are not yet ready for production quality.

See the code below, maybe I’m doing something wrong.


<?php
require_once "ezcomponents/Base/src/base.php";

function __autoload( $className ){
ezcBase::autoload( $className );
}

$sourcedb['host']= isset($_POST['sourcedb']['host'])? $_POST['sourcedb']['host']:”;
$sourcedb['port']= …