![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
How well do todays databases implement SQL99? I dont think any are certified. Will they be? |
#3
| |||
| |||
|
|
How well do todays databases implement SQL99? I dont think any are certified. Will they be? |
#4
| |||
| |||
|
|
How well do todays databases implement SQL99? I dont think any are certified. Will they be? |
#5
| |||
| |||
|
|
How well do todays databases implement SQL99? I dont think any are certified. Will they be? The FIPS-127 Certification program that was administered by NIST was closed down by Clinton years ago. But nobody has a great desire to use the SQL-99 specs as more than a guide for syntax when they add a new feature. The language got way out of hand when it was internally known in NCITS H2 (nee ANSI X3H2) as SQL3. We have about 100 contractions, three different object models, etc. The final results were better, but still a nightmare of non-relational features globbed together. The U.S. government refers to it as "a standard in progress", then asks for SQL-92 conformance in its bids. Remember PL/I? Algol-68? ADA? ^ ^ ^ | it's still alive and kicking with pleasure god, no |
#6
| |||
| |||
|
|
PL/I?: God, no! |
|
Algol-68? with pleasure |
|
ADA? it's still alive and kicking |
#7
| |||
| |||
|
|
PL/I?: God, no! It compiled to over three times the size of a COBOL program to do the same job, and ALWAYS ran. Never mind that you wanted it to stop. The automatic type conversions could suddenly give you a payroll with complex numbers instead of a warning. Algol-68? with pleasure No, no, no. Algol-60 was a pleasure. Algol-65 was a clean up. Algol-68 was so complex that there were only three compilers for it (one was the Royal Radar guys in teh UK and I don't remember the other two -- colleges, I think). I still have the specs for it; I still cannot understand the meta-meta-language they invented. |
|
ADA? it's still alive and kicking Nope. The Ada mandate was killed on 1998 Oct 01. I was with AIRMICS when ADA was created and had to write code in it without a compiler. The thing was awful and the first compilers took a year longer than planned because of the complexity. As InfoTech put it, there was no way to build a kernel then add to it to get a full language compiler -- you had to create the entire language all at once. A New York University built a compiler in SETL which had one error message and we played with that. What we actually did with Ada was write a C or Forth program then drop it into an Ada shell to get real-time systems to work. |
#8
| |||
| |||
|
|
joe.celko (AT) northface (DOT) edu (--CELKO--) wrote in message news:<a264e7ea.0310010946.58a685ae (AT) posting (DOT) google.com>... How well do todays databases implement SQL99? I dont think any are certified. Will they be? The FIPS-127 Certification program that was administered by NIST was closed down by Clinton years ago. But nobody has a great desire to use the SQL-99 specs as more than a guide for syntax when they add a new feature. The language got way out of hand when it was internally known in NCITS H2 (nee ANSI X3H2) as SQL3. We have about 100 contractions, three different object models, etc. The final results were better, but still a nightmare of non-relational features globbed together. The U.S. government refers to it as "a standard in progress", then asks for SQL-92 conformance in its bids. Remember PL/I? Algol-68? ADA? ^ ^ ^ | | it's still alive and kicking | with pleasure god, no robert |
#9
| |||
| |||
|
|
How well do todays databases implement SQL99? I dont think any are certified. Will they be? |
#10
| |||
| |||
|
|
"Ryan" <rgaffuri (AT) cox (DOT) net> wrote How well do todays databases implement SQL99? I dont think any are certified. Will they be? More importantly, why would you want them to implement SQL99 ? |
![]() |
| Thread Tools | |
| Display Modes | |
| |