Edit - Stack Overflow

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*

Rev

A database developer may view application code in much the same way you described stored procedures.

JohnW
– JohnW

2009-03-05 17:32:55 +00:00
Commented Mar 5, 2009 at 17:32
Sure it's going to be hard to deal with if you assume that it's horribly written. I'd say exactly the same thing for C# code - if the developer writes garbage you're going to get garbage.

Tom H
– Tom H

2009-03-05 17:51:37 +00:00
Commented Mar 5, 2009 at 17:51
I would never consider using a "many layered, cursor-looping, temp-table using, many-layered nested stored proc." There are almost always better ways to do business. I think the point JohnW was making was that if you did do such a thing, it would be bad by definition to a database person.

HLGEM
– HLGEM

2009-03-05 18:01:26 +00:00
Commented Mar 5, 2009 at 18:01

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »

Collectives™ on Stack Overflow