Edit - Software Engineering Stack Exchange

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

1

I don't think ANSI SQL was ever the answer. The standard is too large, omits certain important behaviors, and is too vague on key questions. This is one reason that vendor implementations differ so much. Also, while standardized SQL would be a nice start, there would still be a need for a "different query language" that overcomes some of SQL's maddening limitations.

user82096
– user82096

2014-10-03 06:58:20 +00:00
Commented Oct 3, 2014 at 6:58
1

You can level the same argument against any standard, be it HTML, OpenGL or C. The fact that its difficult to make 1 thing fit every vendor's desire for differentiation doesn't mean its not a good thing to have.

gbjbaanb
– gbjbaanb

2014-10-03 07:34:15 +00:00
Commented Oct 3, 2014 at 7:34

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 »