![]() | |
#41
| |||
| |||
|
|
On Nov 19, 2:36 am, toby <t... (AT) telegraphics (DOT) com.au> wrote: [...] (when was the last time you used Erlang or Icon? ![]() When was the last time you used [a spreadsheet] or OOCalc? ;-) |
|
[...] /Lennart |
#42
| |||
| |||
|
|
We are still waiting for the DWIMNWIS computer. I think it will be a long wait. (DWIMNWIS = Do What I Mean, Not What I Say) That isn't the problem. That is exactly what the problem is not. The problem is that a reasonable person (such as the OP of this thread) can write a query that says *exactly* what he means, and it still isn't good enough. He has to discover some equivalent but different formulation, somehow, by no means anyone can explain except by cataloging "tricks that have worked in the past and might continue to work in the future". That is exactly the problem in this discussion. SQL promises to provide correct results, ... The SQL standard, as I understand the situation (I haven't read the real standard, just summaries), leaves optimization or performance features in the hands of the DBMS products. [] To the extent that we have people that are Expert SQL programmers and unable to program in anything else, I would agree that this is a bad thing. Otherwise, I think your optimizer arguement would apply to about any programming language. No, SQL is unlike any other comparably widely used language because it is declarative. Roy You are saying SQL is the ONLY declarative language? I don't think he's saying that. He qualified it with 'comparably widely used'. No 'widely used' programming language is declarative (when was the last time you used Erlang or Icon? ![]() I am not an expert, but other things that I would consider declarative are: - makefiles (commonly used, but hardly considered a 'language') - grammars (lex, yacc) - regular expressions - pattern matching &/or functional languages (Erlang, Mathematica) - backtracking &/or inferential languages (Icon, Prolog) ...additions to this list welcome. |
#43
| |||
| |||
|
|
We are still waiting for the DWIMNWIS computer. I think it will be a long wait. (DWIMNWIS = Do What I Mean, Not What I Say) That isn't the problem. That is exactly what the problem is not. The problem is that a reasonable person (such as the OP of this thread) can write a query that says *exactly* what he means, and it still isn't good enough. He has to discover some equivalent but different formulation, somehow, by no means anyone can explain except by cataloging "tricks that have worked in the past and might continue to work in the future". That is exactly the problem in this discussion. SQL promises to provide correct results, ... The SQL standard, as I understand the situation (I haven't read the real standard, just summaries), leaves optimization or performance features in the hands of the DBMS products. [] To the extent that we have people that are Expert SQL programmers and unable to program in anything else, I would agree that this is a bad thing. Otherwise, I think your optimizer arguement would apply to about any programming language. No, SQL is unlike any other comparably widely used language because it is declarative. Roy You are saying SQL is the ONLY declarative language? I don't think he's saying that. He qualified it with 'comparably widely used'. No 'widely used' programming language is declarative (when was the last time you used Erlang or Icon? ![]() I am not an expert, but other things that I would consider declarative are: - makefiles (commonly used, but hardly considered a 'language') - grammars (lex, yacc) - regular expressions - pattern matching &/or functional languages (Erlang, Mathematica) - backtracking &/or inferential languages (Icon, Prolog) |
|
...additions to this list welcome. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |