Please help save Ivan, son of Andrii Nikitin (MySQL Support Engineer), who needs a bone marrow transplant. Andrii’s message is below:

“My family got bad news - doctors said allogenic bone marrow transplantation is the only chance for my son Ivan.

“8 months of heavy and expensive immune suppression brought some positive results so we hoped that recovering is just question of time.

“Ivan is very brave boy - not every human meets so much suffering during whole life, like Ivan already met in his 2,5 years. But long road is still in front of us to get full recover - we are ready to come it through.

“Ukrainian clinics have no technical possibility to do such complex operation, so we need 150-250K EUR for Israel or European or US clinic. The final decision will be made considering amount we able to find. Perhaps my family is able to get …

Truncating all tables in a database is a common problem which arises a lot during testing or debugging.
One of the most common answers to this question is to drop & recreate the database, most likely utilizing the shell. For example, something like this:

mysqldump --add-drop-table --no-data [dbname] | mysql [dbname]

This dumps the entire schema structure to disk, without dumping any data, and with commands for dropping existing tables. When loading it back into mysql, it essentially truncates all the tables in the database. Basically, this is a decent solution for many uses.

We had a requirement for a solution that needed these additional features:

1. Does not require shell (We work with both Linux and Windows)
2. Resides inside the MySQL Server (To minimize outside dependencies - for example - the mysql command line client)
3. Can truncate only specified tables using a …

Mysql Connector/J (5.1.5, JDBC Driver) is delivered to the OpenSolaris source as part of the Webstack project, and should show up in build 92. The JDBC driver will be located at

/usr/mysql/connectors/jdbc/5.1

So check out OpenSolaris at build 92 ;)

Mysql Connector/J (5.1.5, JDBC Driver) is delivered to the OpenSolaris source as part of the Webstack project, and should show up in build 92. The JDBC driver will be located at

/usr/mysql/connectors/jdbc/5.1

So check out OpenSolaris at build 92 ;)

I spent this past weekend writing a Paper for a project I’ve been playing with. It is a simplified distributed processing system loosely based on Google’s MapReduce, except rather than focusing on larger batch jobs, it prototypes out some common database application uses. The model is currently very basic, but I plan on exploring this further (possibly with a performance-enhanced implementation in C). I’ve also been reading up on other interesting projects like Hadoop, HyperTable, Amazon’s SimpleDB, and of course the DB interface for Google’s AppEngine. I’m wondering how these …

I want to get opinions from outside of my daily circle of people on the best server hardware to use for MySQL. I remember from the conference somebody (Pipes?) mentioning a particular Dell server with multiple disk RAID10 that could supposedly be had for about $6k but I completely misplaced the model number (Frank, did you get my email?).

I know that a multi-disk RAID array with a bunch of fast disks (15k RPM?) is probably the most important method of improving performance, followed by the amount of RAM, so I'm trying to find the best combination/balance of the two. However, server prices on the Internet range so much that I don't even know where to begin to tell a good deal from a bad one. I don't think SSDs can play a role here, because we …

In this post I shall show you how you can set up a MySQL community server on your Solaris installation.

Some useful information:

• Solaris installation: Solaris 10 (32-bit SPARC)
• MySQL 5.1.24-rc is the MySQL community server I am using for the demonstration (You may also try this with MySQL 5.1.25-rc, since the older tarball is not available officially anymore)
  

You will need the following tools:

• GNU Make (gmake): I am using GNU Make 3.80
• GNU C/C++ compiler:
  
  • gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
  • g++ (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
    

• Download the MySQL 5.1.24-rc source tarball from  …

In this post I shall show you how you can set up a MySQL community server on your Solaris installation.

Some useful information:

• Solaris installation: Solaris 10 (32-bit SPARC)
• MySQL 5.1.24-rc is the MySQL community server I am using for the demonstration (You may also try this with MySQL 5.1.25-rc, since the older tarball is not available officially anymore)
  

You will need the following tools:

• GNU Make (gmake): I am using GNU Make 3.80
• GNU C/C++ compiler:
  
  • gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
  • g++ (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
    

• Download the MySQL 5.1.24-rc source tarball from  …

Netbeans 6.1 was released recently which includes PostgreSQL JDBC driver. It had been a while since I had done programming as a developer, so I decided to take it for a test drive to refresh my programming skills with it. Well here is the resulting demo application:

Remember it is just a demonstration application. It requires your client (laptop or desktop ip address) to be trusted in  pg_hba.conf  ip adddress in order to work with your database.

Update on Sept 30,2008: Added a new dialog box which includes option for password and also the new L&F called nimbus (JRE6u10 recommended). Here is a quick screenshot:

Contrary to what I said earlier, Falcon has decided to deliberately disable statement-based replication using the same capabilities mechanism that InnoDB uses.

The reason is that isolation between concurrent transactions cannot be guaranteed, meaning that two concurrent transactions are not guaranteed to be serializable (the result of a concurrent transaction that has committed can "leak" into an ongoing transaction). Since they are not serializable, it means they cannot be written to the binary log in an order that produce the same result on the slave as on the master.

However, when using row-based replication they are serializable, because whatever values are written to the tables are also written to the binary log, so if data "leaks" into an ongoing transaction, this is what is written to the binary log as …