MySQL

TwitterFacebook
Get flash to fully experience Pearltrees
The main goal of the vitess project is to provide servers and tools to facilitate scaling of MySQL databases for the web. The Project Goals page has more details on this. Vtocc is the first usable product of vitess. It acts as a front-end to MySQL providing an RPC interface that accepts and transmits SQL commands.

vitess - Scaling MySQL databases for the web - Google Project Hosting

http://code.google.com/p/vitess/

3 Biggest MySQL Migration Surprises | Architects Zone

http://architects.dzone.com/news/3-biggest-mysql-migration We Recommend These Resources Once a development or operations team gets over the hurdle of open-source, and start to feel comfortable with the way software works outside of the enterprise world, they will likely start to settle in and feel comfortable. Fear not, there are more surprises hiding around the corner. Here are a few of the biggest ones. 1.
Incorrect string value

MySQL Limitations Part 1: Single-Threaded Replication | Architects Zone

http://architects.dzone.com/news/mysql-limitations-part-1 We Recommend These Resources I recently mentioned a few of the big “non-starter” limitations Postgres has overcome for specific use cases. I decided to write a series of blog posts on MySQL’s unsolved severe limitations.

Audit Your MySQL Memory Usage » The Planet Blog

http://blog.softlayer.com/2010/07/19/audit-your-mysql-memory-usage/ We can't seem to find the content you're looking for. It's probably a mistake on our end, so don't feel too discouraged. If you absolutely need to find whatever content you thought you'd find here, leave us a comment on the first SoftLayer Blog entry you can access.
We Recommend These Resources While other Sun projects such as OpenSolaris and OpenOffice.org were driven to make forks (Illumos and LibreOffice respectively) under Oracle's new leadership style, MySQL forks are not in the same position. Oracle seems to be relatively committed to the MySQL community, but this hasn't stopped older forks from moving forward. One fork of MySQL that was started over three years ago is just now reaching beta quality according to the developers. http://css.dzone.com/articles/mysql-fork-drizzle-shows-signs

MySQL Fork "Drizzle" Shows Signs of Life | Web Builder Zone

MySQL is Not ACID Compliant « myNoSQL

This is becoming a “ trend “: That’s because you are basically taking your data and vomiting it on the hard drive without any consideration as to if your data you are writing is sensible or simply dreamed up by magic pixies. http://nosql.mypopescu.com/post/1085685966/mysql-is-not-acid-compliant
I have very strange exceptions, using JDBC-client, UTF-8 for both parties, and LONGTEXT field: 2007-05-22 21:53:16,849 [eshop.macsales.com ] ERROR org.tokenizer.fetcher.FetcherThread - http://eshop.macsales.com/OSXCenter/XPostFacto/Archive/XPostFacto3.1a3.sitx org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [update web_resource set url_actual=?

error code [1366]; Incorrect string value: '\xF4\x80\x80\xB9Bu...'

http://forums.mysql.com/read.php?103,154519,154519#msg-154519
Profiling

MySql deadlocks

MySql tmp tables

Replication

http://jmz.iki.fi/blog/programming/converting_mysql_database_to_postgresql The majority of Open Source applications utilizing a database backend are programmed only for the most common and easy to use RDBMS -- MySQL . Unfortunately, MySQL doesn't offer nearly any of the benefits of a serious database management system, and therefore it's often disgarded when selecting corporate database backends. Selecting something else than MySQL means you exclude many of the fine Open Source applications out there from your corporate (or other) infrastructure -- or then not. Some time ago I wrote a patch to enable an Open Source wiki application to be used with PostgreSQL . Converting MySQL-only software to use some other backend is not hard -- it merely takes a bit of digging to find out how MySQL is not compatible with the SQL standard and how the "tweaks" in MySQL are achieved with SQL-conforming database management systems.

Converting MySQL database to Postgresql

http://architects.dzone.com/news/doom-multiple-storage-engines

The Doom of Multiple Storage Engines | Architects Zone

We Recommend These Resources One of the big “Selling Points” of MySQL is support for Multiple Storage engines, and from the glance view it is indeed great to provide users with same top level SQL interface allowing them to store their data many different way. As nice as it sounds the in theory this benefit comes at very significant cost in performance, operational and development complexity. Let me touch just on the few complications it brings in Conversions – Each storage engine has its own data storage format so MySQL has to do a lot of copying and conversions while accessing the data, which significantly limits performance compared to basically “zero copy” design one may have streaming data from memory when it fits there.