Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 1
    do you mean you want both sprocs on the db at the same time and to be able to call both, but the problem is they cant have the same name? Commented Aug 6, 2019 at 12:02
  • yes thats what i want Commented Aug 6, 2019 at 12:51
  • This seems to be a problem you've caused yourself by using stored procedures. The obvious and simplest option is just to stop using them from now on and keep your SQL in your application. What motivation do you have to continue using them? Commented Aug 6, 2019 at 13:37
  • 2
    @NathanCooper This isn't a stored-procedure-specific problem and can happen without a database being involved. Commented Aug 6, 2019 at 16:59
  • 1
    If your app does not provide for forward compatibility, and your database is unable to provide for backward compatibility, your only option is to force the end user to upgrade their app. Commented Sep 17, 2019 at 1:10