Anybody try the MySQL 5 beta yet?

[oboeguy]

Looks like a light workload today so I'm going to give it a whirl.

 

[FineWine]

Yeah the stored procedures part has got me excited too. I'm still working on getting us MySQL 4 (yeah...I know, I said the same thing) here at work, so I haven't touched on it yet. I might try it at home tonight.

 

[oboeguy]

So it's a couple of months later, anybody? I have a beta running in parallel for testing purposes. I think there's now a "RC" version out now ("release candidate").

A propos, any good places to learn about MySQL 5's stored procedure support?

 

[oboeguy]

Production version is out, wo0t! Now to find a good tutorial on stored procedures...

 

[Armitage]

Our new database server is supposed to be here "any day now" so I may experiment with it a bit before putting it in service.

 

[oboeguy]

Bah, no good info online that I could find on stored procedures. There's at least one book out listed as in-stock at BookPool.

Edit: MySQL's looong PDF on stored procedures. Looks like a good place to start!

 

[oboeguy]

That document I linked was actually not that useful. Those guys could use an editor, trust me.

Anyhow, stored procedures are good to go. Be sure to update the MySQL ODBC driver if that's what you're using, because otherwise you may have problems with SP's.

 

[kamper]

For anyone who's fooled around with them, how is the language? I mean, I cringe at the thought because I've always found writing mysql sql to be comparatively painful and stored procs in general are painful when compared to more general programming languages. At least when silly developers try to do business logic in the procs...

 

[oboeguy]

Originally posted by: kamper
For anyone who's fooled around with them, how is the language? I mean, I cringe at the thought because I've always found writing mysql sql to be comparatively painful and stored procs in general are painful when compared to more general programming languages. At least when silly developers try to do business logic in the procs...

At my current job I do a lot of data mining so it's pretty natural to put the logic into the SPs. I've really only started to play with it, but I expect to speed-up my applications a lot. Moving loops into SPs when doing zillions of iterations should be a huge performance boost.

 

[kamper]

Originally posted by: oboeguy

Originally posted by: kamper
For anyone who's fooled around with them, how is the language? I mean, I cringe at the thought because I've always found writing mysql sql to be comparatively painful and stored procs in general are painful when compared to more general programming languages. At least when silly developers try to do business logic in the procs...

At my current job I do a lot of data mining so it's pretty natural to put the logic into the SPs. I've really only started to play with it, but I expect to speed-up my applications a lot. Moving loops into SPs when doing zillions of iterations should be a huge performance boost.

I'm just saying that sql + stored proc extensions are built for manipulating a database, not general purpose computing and busines logic, so it's inevitably a bit ugly. I'm not saying you should never do it. It's kind of like the trade-off between programmer power and computer power. As computers get faster, the programmer becomes the weak link and we try to use tools that push the extra work off on the computer. But if you're in a situation where you can improve performance safely by doing it the hard way then it's got to be done I just don't want to be the one doing it