MySQL Bugs: #15975: Optional parameters support in stored procedures

Bug #15975	Optional parameters support in stored procedures
Submitted:	24 Dec 2005 16:49	Modified:	25 Dec 2005 6:22
Reporter:	Roberto Meardi	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Stored Routines	Severity:	S4 (Feature request)
Version:	5.0, 8.0	OS:	Windows (Windows)
Assigned to:		CPU Architecture:	Any

Description:
I've been using MSSQL for a couple of years. I write almost all the sql statements in stored procedures, so I can encapsulate data logic, that can be changed later without recompiling my application.
In MySQL v5.0 you came out with Stored Procedure support, so I downloaded it and began using it. Currently I'm translating my stored procedures in mssql to mysql. But I've come with a BIG problem. MySQL stored procedures do not support optional parameters, so, if I want to change my undelying database system, I'd have to write almost all the data access layer for my applications.
This is why I'm requesting Optional Parameters support for Stored Procedures...

How to repeat:
Feature request

Thank you for a useful feature request. By optional parameter you mean the one with default value, I believe... So, that the value for it can be ommited in the SP call. Oracle's PL/SQL also has this feature. I think it should be implemented as soon as possible to simplify migration from other RDBMS to MySQL 5.

Please advise of the status of this bug. Has this been implemented yet? If so, what version of MySQL is it available in? And if not, why not?

I cannot stress enough the importance of such!
Any plans for implementing this???
Meir

I would also like to add my request for this addition as well as I cannot find any reference to this in current versions.

Bug #60355 was marked as a duplicate of this one.

Wow, this bug is from 2005 and the MySQL team hasn't decided to fix it yet? 
I would like to bump this, since I think it's a needed feature.

Please implement this feature.

Yes, please do this! Every comment so far is in support of this important feature. Over five years have passed. Thanks!

Please support this ASAP! This is really inconvenient.

It would be really nice to have default values. Please add this feature asap.

http://bugs.mysql.com/bug.php?id=67201 is a duplicate

Dear god, PLEASE implement this.. 
This would make my work load SOO much easier to handle.

I really don't understand why this feature hasn't been implemented yet. =/

Please do implement this. It would be very useful for MySQL to have this simple feature that is available in most mature databases.

bug #71765 is a duplicate

Please add this feature. Almost 10 years since it was first formally requested.

It's very disappointing me.
kindly add this features ASAP.

Thanks in Advance.

This would be a great feature for backward compatibility. I'm surprised it's been on the ToDo list for almost 10 years. Any chance of this happening?

Ten years already...

Why is this so difficult to implement? 
This is supported by all modern systems, and indeed it would be very useful. 
Can we get some information about whether the resolution of this problem come to the table and when? 

Thanks in advance.

Please do implement this. It would be very important for MySQL to have this simple feature that is available in most mature databases since many years.

I have literally created an account just to request this feature.
It seems crazy that the syntax exists in the language yet there is this restriction on what should be a simple implementation - c'mon Oracle show us you are listening :)

This functionality is needed. Please add my vote.

I will add my vote as well.  I primarily use MySQL, so I have little concern with porting from other platforms.

My main reason is for maintainability when there are many client systems.  If a procedure update is made requiring an additional parameter, the installed base will throw an error when the parameter is not present, thus requiring simultaneous updates for all client installations.  

The obvious work-around is creation of a new procedure with a different name, but I find that disagreeable because of the proliferation of procedures with essentially the same functionality.

Please can we have an update from MySQL on this issue. This is a serious shortcoming of MySQL database.

I, like others, are converting stored procs from MSSQL to MySQL and this missing feature is problematic.

Please can we have default values for parameters.

12 years later.....

still no updates if this is supported yet?

Agreed - I'm moving some databases from MSSQL to MySQL - almost sorry I'm doing so with optional parameters missing.  Even a default value would help simplify things.

+1 - My company develops for both MSSQL and MySQL platforms. The lack of this functionality makes the MySQL implementations harder - the delivery on this platform always lags behind MSSQL.

+1 - My company develops for both MSSQL and MySQL platforms. The lack of this functionality makes the MySQL implementations harder.

LoL. 13 years.

Please do implement this!

Please implement this feature.

This is an absolutely required feature. And from the looks of it, I'd imagine it's not too hard to implement.

But yet if it's not getting implemented even 15 years after after requesting for it, then I can only surmise that the reason is that Oracle wants its flagship Oracle database product to retain some competitive feature edge over the MySQL database product. Else there may not be too many takers for its flagship product, if what it gives away for free starts coming closer in feature-list to its flagship paid product!

From one point of view, thats quite understandable.

still no change on this ?????

still unsupported?

Bug #109754 marked as duplicate of this one