Yeah...title says it all.
Bug bug #11661, Raising Exceptions from within stored procedures: Support for SIGNAL statement.
I can't recall the exact moment of filing this bug, because I filed a lot of them. However, this one is special to me because I filed it when I was in the process of getting involved with MySQL and its community. I remember it as a very intense period of learning, meeting other community members online (mostly through forums.mysql.com and blogging on a regular basis.
A lot has happened since then, and if you ask me, most of it is good stuff. The only thing that casts somewhat of a shadow is that it took so long to fix this. But I don't want to whine about it. Rather, I'd like to use this opportunity and extend my big, BIG THANK YOU!! to Marc Alff who has been working very hard on implementing this feature. I should also mention Peter Gulutzan, who's enduring attention to quality and efforts for making MySQL comply more to the SQL Standard have made MySQL a better product.
Thanks Guys! I'm looking forward to using this and other features in MySQL 6.0.
Subscribe to:
Post Comments (Atom)
DuckDB bag of tricks: Processing PGN chess games with DuckDB - Rolling up each game's lines into a single game row (6/6)
DuckDB bag of tricks is the banner I use on this blog to post my tips and tricks about DuckDB . This post is the sixth installment of a s...
6 comments:
Woot! indeed! Now we don't have to do anything weird like assigning a string to a local variable declared as an integer, or setting a not-null column to null.
Maybe someday MySQL will support check constraints too.
June 2005.
For those adventurous to try patches against MySQL 5.1, a Perl Stored Procedure can use 'die' to report custom error messages to the client.
Whoohoo!
Good news indeed!
Together with "DECLARE EXIT HANDLER" and "DECLARE CONTINUE HANDLER" we get a true exception handling mechanism (albeit not too pretty)
It is a tremendous shame that this couldn't be done in 5.1. MySQL AB stupidly went RC way too early, essentially feature-freezing development for nearly two years.
I am not sure what the whole point of 5.1 is. Partitioning is crap, EVENTS are crap (especially without SIGNAL!), log tables are crap and the list goes on...
Wow, this is a big step forward in my opinion. I know it seems like a minor thing but being able to do this is very important in my view.
Post a Comment