0
Fixed

Stored Procedure Paramaters are re-sorted following their NAMES !!!

Thomas LEILLET 1 year ago updated by Retinder Labana 8 months ago 5

Hello, the definition of stored procedures is changed by SqlDBM because the sorting of the parameters is rearranged alphabetically based on variables name  !

Basic example : the definition clearly states that "V_Z" is param 1 and V_A is param 2 - the forced sortingmesses with the comparison because in the comparison Pane, if parameters types are different, there will be some gap noticed without any reason, or gap not noticed


PIC 1 : parameters sorted against the proc definition itself.

Image 2324

PIC 2 : comparison left hand pane do not respect the order, and it creates issues in comparison

Image 2325

An example in my project, where my DB and my Project have the same Proc, but the comparison pane think proc are different because of the parameter name sorting affecting the param type sorting, hence the proc definition : on both side, SqlDBM consider no matching (one added, the other missing, whereas they are the same and totally eligible for gap comparison)

Image 2330

Hello, any update on that ?

Under review

Hi Thomas, I apologize. Looks like we missed this one. Adding into our queue and will get an update asap for you. 

Started

Hi Thomas, 

Thanks for reaching out to us. I would to inform you that you have helped us discover a bug. 

Bug: the order of the parameter is changed from how it is brought in (RE) vs what is shown in SqlDBM. 

The bug has been passed to the products team. We will keep you updated on the progress. 

Thanks, 
Retinder Labana

Hi Thomas, 

I would like to inform you that we have fixed this bug. Please note all new versions will respect the order of parameters. 

I have tested this on my end and I do not see this issue anymore. Please let me know if the issue has disappeared for you as well. 

Thanks, 
Retinder Labana