MySQL 4 Declared Production-Ready

Simprini writes "After absolute ages of testing MySQL 4.0.x in various versions of BETA through GAMMA it looks like MySQL AB finally released MySQL 4.0.12 as ready for prime-time production use. I know my company has been waiting for a long time for this because our customers absolutely refused to use beta releases of this product. Query caching here we come."

Comments

Uh oh

[grub]

MySQL 4.0.x in various versions of BETA through GAMMA

Uh oh.. I flat out refuse to use code that isn't ALPHA... well at least as an OS on my Windows machine.

from the hardly-any-data-loss dept ?

[tweder]

Oh that's reassuring!

Excellent.

[Anonymous Coward]

My MySQL 4 worm is also ready for your production environments. Get ready, sucka!

MySQL Query

[NewbieSpaz]

Select * from "http://www.mysql.com/downloads/" where "version" = "mysql-4.0.12"

SELECT version FROM mysql WHERE ready='true';

[Anonymous Coward]

Error : no rows returned.

Alpha Beta Gamma

[L. VeGas]

If it's good enough for such a reputable fraternity, it's good enough for me.

Re:Simply powerful or powerfully simple?

[Anonymous Coward]

Views? They are for people who don't know how to write queries. Triggers? They are for people who like mysterious things to happen to their data.
Foreign Keys? They are for people who don't like to delete their data.
Interval Datatypes? They are for people who are iffy.
Full Outer Joins? They are for people who like lots of data.
Subqueries? They are for people who can't program simple loops.
Set operations? They are for people who can't relate.

Re:Simply powerful or powerfully simple?

[JohnDenver]

Views? They are for people who don't know how to write queries.
Triggers? They are for people who like mysterious things to happen to their data.
Foreign Keys? They are for people who don't like to delete their data.
Interval Datatypes? They are for people who are iffy.
Full Outer Joins? They are for people who like lots of data.
Subqueries? They are for people who can't program simple loops.
Set operations? They are for people who can't relate.

shall I add???

Programming Languages They are for people who can't read machine code in hex.

(I realize you're kidding, but there are some people who might take you seriously)

Re:Its Stable

[CableModemSniper]

Allright, now I *know* not to upgrade. (kidding)

Re:ON DELETE CASCADE

[Troll_Kamikaze]

welcome to real *relational* databases

Easy there, you'll scare the puppy.

Uh oh, the Boss

[Anonymous Coward]

I sure hope my boss doesn't hear about this. I told him we weren't using ANY pre-release software on our production boxes. ;-)

Re:Apparently 90% don't need those features.......

[pi_rules]

After all, PostgreSQL has triggers, stored-procedures, functions, referential integrity, and tons of other features to make your life easier. You may not need all of these features now, but can you honestly say your app won't expand and require advanced features?


Gimmie a break dude. I'm sick of hearing all this stuff about triggers, sub selects, and stored procedures. I can honestly say that no database really needs these things.

In my 6 months of professional development at a 3 man shop I think I'm perfectly well qualified to say that no RDBMS will ever need these futures. I can't possibly imagine a design so fubar that it would EVER have to rely on the RDBMS to enforce such rules. That's what application level code is for! Sheesh!

Well, maybe such things would be useful if you had more than one application pointing at the same database... or if you planned to maintain the DB's integrity over any length of time. But that kind of shit never happens in the real world. It's a made up story of Slashdot posts and database classes.

Given that text doesn't relay voice inflection very well: The above is sarcasim.