MySQL 5.1 Improves Performance, Partitioning, Bug Fixes 146
kylehase writes "CIO.com has a writeup about MySQL's 5.1 release planned for next week. Among the enhancements are many bug fixes from 5.0, some of which may increase performance 20% or more, as well as 'partitioning, events scheduling, row-based replication and disk-based clustering.'"
Disk Clustering (Score:3, Interesting)
License status. (Score:2, Interesting)
When shall we get a decent front end? (Score:3, Interesting)
In my opinion, the day MySQL will have a fully programmable front end...I mean one that a programmer can add business logic to, program input masks, direct functionality at widget or control level and use to generate customized reports depending on various metrics, MySQL will kick ass. Right now, all front ends to MYSQL suck big time and there does not appear to be an end in sight - sadly.
SQL Maestro is very promising but it's not free!
Re:When shall we get a decent front end? (Score:3, Interesting)
SQL Maestro is an administrative tool, not a report generator.
PHP Generator for MySQL [sqlmaestro.com] is free and useful for generating simple database-driven web sites.
Admittedly, the MySQL Query Browser is clunky, but at least it finally works. For several releases, it was badly broken.
Re:It's nearly caught up to PostgreSQL. (Score:1, Interesting)
Re:It's nearly caught up to PostgreSQL. (Score:3, Interesting)
Don't get me wrong, I like the idea of SQLite. Per-user databases are needed very badly. I just wish SQLite performed better on normal sized data sets.
Re:It's nearly caught up to PostgreSQL. (Score:5, Interesting)
MySQL fails at some very critical points. As I said in previous post it fails to fire triggers on updates.
Also MySQL believe its better to serve a best effort than a failure - this is probably the biggest NO GO! out there. YOU NEVER EVER do something other than requested in a database. If the transaction model fails you are using no more than an advance file pointer.
Now PG is a very nice database, they got all the right things implemented, and often better than the competition.
PG however does not have any support for scaling, if you want to scale you need some form of middleware to handle it - and currently you have to buy continuent for that - which is a nice product, they however don't support stored procedures and triggers.
And please don't just hit google for PG and scaleability, and come back saying there are all sorts of products out there - most of them are based on triggers and some very bad methods for propergating data - all of them lack the ability to take down primary or secondary server(s) in a running environment and put a new up without interruption in the data flow.
That line alone tells me you got your head so far up your OSS arse you are seeing pink elephants.
IBM Denmark just went down this week for a whole day, pretty sure their big clients are a bit unimpressed in their failure to bring multimillion installations back online.
If postgres can handle your situation then fine, but in my environment a database failure means everything comes to a grinding halt. And when you promise clients 99.999% uptime you sure as hell need subsecond failover *hint you can't do that with anything that reads binary logs from primary* and zero loss of transactions.