MySQL 5.0 Now Available for Production Use

chicagoan writes "MySQL AB today announced the general availability of MySQL 5.0, the most significant product upgrade in the company's ten-year history. The major new version delivers advanced SQL standard-compliant features such as stored procedures, triggers, views & new pluggable storage engines. Over 30 enterprise platform and tool vendors have also expressed enthusiastic support for the new release of the world's most popular open source database."

Comments

Re:what the?

[b0r1s]

'General' implies usability in production systems. What you really want to read it as is this is the first non-beta release.

We tested many of our sites (including my personal favorite, vobbo, a site for video blogs) and found some very significant speed improvements, especially in some of the math functions (SIN, COS, etc).

Re:Generic Web-Frontends for MySQL

[FireFury03]

This is slightly off-topic, but I was wondering if anyone is aware of any generic web-frontends for MySQL?

How about http://www.phpmyadmin.net/?

Re:stored procs and triggers, finally

[User 956]

Almost every database out there impliments an ISO or similar SQL standard as it's base (SQL-92 in most cases). They then build on top of that by adding their own features, while still supporting the common SQL syntax. It's not about being a barebones implimentation of a standard, it's about supporting the standard as your base.

PostgreSQL supports SQL-92, while adding it's own extra features (which describes most other databases like Oracle and MS SQL too), including the support of the "LIMIT" statement. MySQL doesn't support any standard base, instead existing as an arbitrary mish mash of standard and propritary SQL. It wasn't until the current version, 4, that MySQL even bothered to add support for UNION.

With every other database you can start working safe in the knowledge that while having it's own extensions, you're working with a normal "SQL" database. MySQL, while posing as SQL, has little if anything in common (in particular see threads about optimization - getting fast code in MySQL means learning an entirely new system filled with quirks and vomit inducing workarounds to solve language faults)

phpMyAdmin

[smelroy]

I'm not sure about reporting specifically, but phpMyAdmin is the way to go for a generic MySQL front end.

Re:stored procs and triggers, finally

[temojen]

And if its in your code, the query executes using the resources of the machine running your code, as opposed to the resources of that (usually) bigged database server.

This is so wrong it made my head explode. All queries are executed in the server. Stored procedures are compiled and optimized once (per connection, and most sites use connection pooling).

Re:Innovation

[b0r1s]

Postgres was free ('as in beer') and free ('as in a real license'), and gave away these features long ago.

Besides, for 'freedom', the BSD license used by Postgres beats the GPL hands-down.

Re:stored procs and triggers, finally

[JoeD]

With hardcoded SQL, you run the risk of SQL injection exploits, unless you're very careful to escape each and every user-written field that makes its way into a SQL statement.

Re:stored procs and triggers, finally

[commanderfoxtrot]

You should always use bound placeholders in SQL. Then you don't get SQL injection exploits.

i.e. define a parameter then execute: SELECT x FROM y WHERE p = '?'

It is also faster as the DB can use an already prepared query plan.

This is the ONLY way to write decent SQL applications?

Re:stored procs and triggers, finally

[msuzio]

That would be what prepared statements are for. No need to use stored procs just for that.

Re:Almost caught up to MSSQL!

[TheKubrix]

I hope someone mods the parent down, because thats just stupid/ignorant.

I've been running MS SQL 2000 for about 4 years now and it has NEVER crashed. Nor has it corrupted any data or any other such destruction.

I notice that its people that either have _NO_ database experience tend to bash MSSQL, and they don't even know why. Your comment is a case in point.

Re:Innovation

[Jamesday]

10.0.0.101 is Adler. Its uptime is currently 2017391 seconds (23 days). Adler's uptime is that short because it had a hardware repair. It was probably overload - several DB servers are dead right now and Monday is the busiest day for the site. So far the site is consistently filling to capacity all the hardware which is ordered and that shows no sign of stopping. It's now at 4500 pages per second, 400 megabits/s. For scale, the biggest Slashdotting the site saw was about 650 pages per second.

Averages over 23 days for this one server: 1620 selects per second, 10 inserts and 3 replaces per second. That is: 140 million selects per day average. Peak rates are about double average rates, typically in the 3000-5000 qps range.

I'm one of the roots at Wikipedia. Figures from SHOW STATUS just before typing this reply.