Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
infekted4898yFirst debug only the four lines.
Secondly debug the rest of the goddamn 174 lines.
Those last 2 lines are never buggy.;) -
azzuwan1818y"how do humans debug a 180 lines stored procedure :/ ? "
The standard industry practice way is to do it with a lot of profanity followed by a silent prayer for an office fire. -
ridecar23828y180 lines... that's so adorable! In an old job I had to edit one that was over 1000 lines.
-
Razze568yYou haven't seen anything. I hate to brag about this, but unfortunately I've seen some really long procedures. :(
-
yousefjb1258y@ridecar2 I forgot what that procudere does before reaching line 100 :/
it is hard to debug because you can't see where did the error happen.
I had to copy a few lines at a time and execute them, check the result and copy into the next chunk of lines. -
Hultan704668yI feel your pain, that is why I am so glad that I work with Entity Framework in my latest project. No SQL in sight...:-)
how do humans debug a 180 lines stored procedure :/ ?
undefined