Thank you Ben. I realize there maybe an issue there. I was thinking someone came up with a workaround (sort of speaking). In either cases, I think labels would work well to test partial huge routines, but it will only alter the starting point, not end.
Thank you, I think that will work. Adding a label does not seem to interfere with routine flow, so at least you can run a unit test starting from anywhere, but you still will have to run the routine to the end.
Either way, this is definitely an option if you wish to run a unit test from some point other the starting label.
Thank you Robert
Thanks Tim, that works.
Thank you, that makes perfect sense.
Thank you for clarifying, that is what I ended up doing.
Thank you Robert.
Maybe this is not the best answer, but there are detailed explanation with examples of conditional sql here: https://www.geeksforgeeks.org/sql-conditional-expressions/
I hope this helps,
Thanks,
Alex
Thank you Ben. I realize there maybe an issue there. I was thinking someone came up with a workaround (sort of speaking). In either cases, I think labels would work well to test partial huge routines, but it will only alter the starting point, not end.
Thank you, I think that will work. Adding a label does not seem to interfere with routine flow, so at least you can run a unit test starting from anywhere, but you still will have to run the routine to the end.
Either way, this is definitely an option if you wish to run a unit test from some point other the starting label.
Thank you,
Alex
Thank you Robert.
That worked, and thank you very much for the explanation. I would not guess something like this. Great to know,
Alex
I meant - I guess what would be the benefit to use class method [private] vs regular method [private] here?