Did you know that many parts of the MySQL web sites provide news and updates via RSS Feeds? Markus Popp from our web team did a great job on making some of these more visible by adding RSS icons to the respective pages. If you want to keep up with what's happing at MySQL, consider adding the following feeds to your feed reader:
Replication is one of the most flexible technologies available
for databases. We are implementing a new open-source,
database-neutral replication product that works with MySQL,
Oracle, and PostgreSQL. Naturally we've done a lot of thinking
about the feature set. It's tough to pick any single feature as
the most important, but one that really stands out is optional
statement replication. Here's why.
Database replication products tend to replicate row changes and
DDL. However, Mark Callaghan has a great example of why you want to replicate
statements as well--it enables Maatkit distributed consistency checking to
work. If you dissect the …
The modification of PDO_MYSQL to support the MySQL native driver for PHP (mysqlnd) is progressing. We are using the project title “PDO_MYSQLND” for the modification. The goal of PDO_MYSQLND is to provide a PDO driver for MySQL which can be compiled either against the MySQL Client Library or against the MySQL native driver for PHP. This is the same type of modification we did with ext/mysql and ext/mysqli already.
The use of any of the libraries is transparent for the PHP user. You may continue to use the MySQL Client Library, like you do today with PDO_MYSQL, or give mysqlnd a try. The MySQL native driver for PHP (mysqlnd) is easier to compile as its tightly integreated into the PHP internals and ships with PHP as of version PHP 5.3. In case of ext/mysql and ext/mysqli our benchmarks and first user feedback indicates that mysqlnd gives you at least the same performance of libmysql. And sometimes it is faster and more memory efficient. …
[Read more]The modification of PDO_MYSQL to support the MySQL native driver for PHP (mysqlnd) is progressing. We are using the project title “PDO_MYSQLND” for the modification. The goal of PDO_MYSQLND is to provide a PDO driver for MySQL which can be compiled either against the MySQL Client Library or against the MySQL native driver for PHP. This is the same type of modification we did with ext/mysql and ext/mysqli already.
The use of any of the libraries is transparent for the PHP user. You may continue to use the MySQL Client Library, like you do today with PDO_MYSQL, or give mysqlnd a try. The MySQL native driver for PHP (mysqlnd) is easier to compile as its tightly integreated into the PHP internals and ships with PHP as of version PHP 5.3. In case of ext/mysql and ext/mysqli our benchmarks and first user feedback indicates that mysqlnd gives you at least the same performance of libmysql. And sometimes it is faster and more memory efficient. …
[Read more]
The db4free.net's MySQL 6.0 server is at the very
latest state again. I have compiled the server from source, so
you can test the very latest of MySQL development.
Unfortunately there were some issues with the former version
(6.0.4) and I didn't manage to simply upgrade the server as I
used to. After upgrading, the server didn't start up with the old
data directory and dumping database by database to re-import it
into the new version resulted in frequent crashes. After multiple
failures to do a straight update I decided to install a fresh
and empty new 6.0 server.
Now the most important question for you if you used the 6.0
server: where did my data go?
I left the old server up and running, but configured it to port
3308. This means, if you had data in your MySQL 6.0 database, you
can still access it - here's how, if you use the default …
It's been a while since the last post. This is mostly due to me entering new territory in several ways. For one, I have been digging into JavaME development lately (platform change #1), building a mobile data entry and manipulation application that uses a an embedded database and talks to its server via Webservices, if connected. Otherwise data will be queued up locally and sent as soon as the
The modification of PDO_MYSQL to support the MySQL native driver for PHP (mysqlnd) is progressing. We are using the project title “PDO_MYSQLND” for the modification. The goal of PDO_MYSQLND is to provide a PDO driver for MySQL which can be compiled either against the MySQL Client Library or against the MySQL native driver for PHP. This is the same type of modification we did with ext/mysql and ext/mysqli already.
The use of any of the libraries is transparent for the PHP user. You may continue to use the MySQL Client Library, like you do today with PDO_MYSQL, or give mysqlnd a try. The MySQL native driver for PHP (mysqlnd) is easier to compile as its tightly integreated into the PHP internals and ships with PHP as of version PHP 5.3. In case of ext/mysql and ext/mysqli our benchmarks and first user feedback indicates that mysqlnd gives you at least the same performance of libmysql. And sometimes it is faster and more memory efficient. …
[Read more]
Finally got my copy of High Performance MySQL 2nd ed two days
ago.
Yesterday I vaguely remembered Baaron asking if
DPM had a homepage. So I flipped through the book
a bit, and sure enough, on page 599, is a short mention of my
proxy!
Thanks, Baaron! With the upcoming release of DPM it'll be
exciting enough to be worth having a link in your awesome book :)
The mysql proxy project has tremendous potential to
make mysql administration and usage easier. I decided to throw
some load at it to get a feel for how stable and performant it
is.
On EC2, I set up 6 “small” images in an example proxy
setup:
- One client machine to run sysbench
- One machine to act as a mysql proxy machine, running 0.6.1 (FC4
binary)
- Four identical database servers, running mysql 5.0.45
The database configuration was largely default, with InnoDB
configured for 64MB buffer pool (just enough to ensure the
sysbench table was entirely in memory), 512MB log files, and 1024
max connections.
mysql-proxy was run with the following command:
mysql-proxy
–proxy-backend-addresses=ip-10-251-66-63.ec2.internal:3306
–proxy-backend-addresses=ip-10-251-71-21.ec2.internal:3306 …
Berlin has a long history of blooming user groups and the Erlang User Group Berlin will be no exception!
That’s right, Germany’s capital and one of the nicest places to be in Europe (among all the other nice places, hooray for plurality) finally has place for Erlang enthusiasts. That is in fact a pleonasm, I haven’t found a single soul yet who is not enthusiastic about working with Erlang, but what do I know?
Anyway.
Join the discussion group and help to pick a date for meetings.
If you are an Erlang developer on visit in Berlin, let us know, so we can have an out-of-order meeting with you.
Sorry if that shows up at a seemingly non-related planet feed, this is a spam measure and won’t happen again. Thanks for your patience.