Ideas, releases, practical guides, and perspectives from the people building with MySQL.
I’m back in the blogosphere!
This blog will focus on Smalltalk (mostly Pharo, Squeak, Dolphin, VAST and VW), databases (usually MySQL, PostgreSQL, SQL Server, DB2, InterBase and Firebird), algorithms and open source tools. I’ll throw in some literature, music and mathematics occasionally.
Requirements to enjoy this blog : an interest in problem solving, a database and a Smalltalk environment!
There have been a few great blog posts recently from MySQL bloggers about Postgres, and vice versa, with good comments and follow-on from the real experts in both systems. I think this is wonderful. Learning how other databases solve hard problems is highly educational, especially because ACID databases face some of the hardest problems in computing. Making MySQL better is good for PostgreSQL. The reverse is just as true. And we should also be learning from SQLite, and CouchDB, and others who have overcome tough technical hurdles, built successful companies, created thriving and enthusiastic communities, or whatever their success has been.
Related posts:
[Read more]
Alaric
Snell-Pym discusses why choose between SQL and NoSQL? Why can't
you use both in your infrastructure?
"NoSQL engines abandon SQL for the chance to have more flexible
data models and softer semantics for update operations - but they
also abandon it because it’s a lot of work to implement. And,
creating a new database from scratch, they’re keen on solving the
interesting hard problems (such as replicated data storage),
rather than following the well-trodden path of writing SQL
parsers and query planners, with a few decades of catching up
with the competition ahead of them."
MyQuery 4version 3.4.1 is now released on Sourceforge: http://sourceforge.net/projects/myquery/. This is
a pretty minor release with just a few fixes, but the first of
them pretty significant:
The more I go through others SQL, there are some common mistakes that I see developers making over and over again, so I thought why not start a series of tips that can help developers optimize their queries and avoid common pitfalls. So this post is a part of that series of tips, and this is the first tip "Avoid using a wild card character at the start of a LIKE pattern".
Here's what's new for the trendy developer this week:
Java's future on Apple: Slightly less in doubt
Last week, it looked like Apple was all "You're not welcome here, Java." In the changeable world that is Jobsland, this week Apple was offering to marry the language, reiterating their support for Java in OS X, and indicating that they would be supplying code and resources to the OpenJDK project.
As I've noted before, this makes sense for Apple, because it gets them out of the JVM business, and makes Oracle the one-stop shopping solution for all your JDK and JRE needs. It also means that the Mac can be added as a regression-tested target for a new version of Java, hopefully avoiding the kind of Java versioning snafus that rendered IBM's SPSS (or is it PAWS this week?) statistics …
[Read more]I’ve started an HTML manual for innotop, a “top” clone for MySQL. It includes screenshots. Right now I only have screenshots for the new U mode, which demonstrates how the User Statistics enhancements in Percona Server can show you which tables and indexes are most used.
No related posts.
This month’s Maatkit release, which just hit the download servers, contains a new feature for mk-query-digest: Apdex scores. The Apdex performance index is a sensible metric of how satisfactory the response time to a request is. Of all the scientific metrics I’ve seen, it’s the most practical; and of all the practical ones I’ve seen, it’s the most scientific.
To use this feature, you need to know what the Apdex threshold means, and you need to know how to configure this in mk-query-digest.
And then you can ask and answer practical questions such as “which classes of queries against this MySQL server are not satisfying users?” Or, because mk-query-digest supports the HTTP protocol, you can pose …
[Read more]I’ve just uploaded the new release of innotop to Google Code. Short version of the changelog: works on MySQL 5.1 with the InnoDB plugin; more efficient; supports Percona/MariaDB USER_STATISTICS data; fixes a bunch of small annoying bugs.
Longer version:
2010-11-06: version 1.8.0
Changes:
* Don't re-fetch SHOW VARIABLES every iteration; it's too slow on many hosts.
* Add a filter to remove EVENT threads in SHOW PROCESSLIST (issue 32).
* Add a timestamp to output in -n mode, when -t is specified (issue 37).
* Add a new U mode, for Percona/MariaDB USER_STATISTICS (issue 39).
* Add support for millisecond query time in Percona Server (issue 39).
* Display a summary of queries executed in Query List mode (issue 26).
Bugs fixed:
* Made config-file …It’s been ages since we’ve had an update to innotop, or at least, it’s been a while since the changes were bundled up and released officially. Barring any bug reports against the trunk code, I’m about ready to release more than a year’s worth of improvements to it:
Changes:
* Don't re-fetch SHOW VARIABLES every iteration; it's too slow on many hosts.
* Add a filter to remove EVENT threads in SHOW PROCESSLIST (issue 32).
* Add a timestamp to output in -n mode, when -t is specified (issue 37).
* Add a new U mode, for Percona/MariaDB USER_STATISTICS enhancements (issue 39).
* Add support for millisecond query time in Percona Server (issue 39).
* Display a summary of queries executed in Query List mode (issue 26).
Bugs fixed:
* Hostname parsing wasn't standards compliant (issue …