Timeline for Check which condition has met - Sql Server
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16, 2018 at 21:04 | history | edited | Jelther Gonçalves | CC BY-SA 3.0 |
added 166 characters in body
|
| Jan 16, 2018 at 21:03 | comment | added | Mr.Brownstone | If you have 500+ checks within a single function then I would recommend re-engineering some if not all of the call-stack. If you cannot do that, then you are left with returning a different code per check - which then you have to handle in the calling layer. So then you have 500 checks for a return code. Its a no-win scenario... | |
| Jan 16, 2018 at 20:58 | comment | added | Jelther Gonçalves | It is! I had this idea but I was expecting something different since I have +500 conditions. Changing all them would require a lot of time. | |
| Jan 16, 2018 at 20:58 | comment | added | Jelther Gonçalves | It is! I had this idea but I was expecting something different since I have +500 conditions. Changing all them would require a lot of time. | |
| Jan 16, 2018 at 20:47 | answer | added | Rob Farley | timeline score: 1 | |
| Jan 16, 2018 at 20:04 | comment | added | Mr.Brownstone | Are you able to return a different code per condition? That would be the easiest solution. | |
| Jan 16, 2018 at 20:02 | history | asked | Jelther Gonçalves | CC BY-SA 3.0 |