| Title: | DEC Rdb against the World |
| Moderator: | HERON::GODFRIND |
| Created: | Fri Jun 12 1987 |
| Last Modified: | Thu Feb 23 1995 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1348 |
| Total number of notes: | 5438 |
Still working on a competitive situation with O (now in protest phase)
and trying to increase understanding of what they did. A couple of
questions:
(1) Oracle claims that version 6.0 and 6.0.27.1 are basically
identical (only a few minor "bug" fixes). Does anybody know anything
about this? Any info is appreciated.
(2) Oracle used SELECT statements in their SQL to return sets. The
SELECT would return data into fixed-length arrays and then SQLERRD[3]
was used as if it contained the number of rows returned. We opened
cursors, fetched rows, and closed cursors to accomplish something
simliar. Is the use of SELECT for set processing common to SQL? (I've
never seen it before in a program, but I am not an expert...) Is this
standard SQL (per ANSI)? Is it an ORacle extension?
Thanks for any suggestions,
Rusty.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 927.1 | Oracle extension...not standard feature | COOKIE::MELTON | The zen of character sets | Wed May 08 1991 18:43 | 15 |
Rusty, Oracle's use of the SELECT to identify and retrieve multiple rows simultaneously into an array is *NOT* ANSI- or ISO-standard SQL. There is nothing in SQL2 that would support that, either. That is strictly an Oracle extension. Feel free to use that in your competitive situation by pointing out that Digital's SQL is standard and Oracle has to depend on vendor-specific extensions; mention that this will lock the customer into Oracle's product and they'll lose any benefits of "openness". Of course, don't push that line *too* hard, because Digital has its own vendor-specific extensions that we use as enticements to buy Rdb/VMS and VAX SQL ;^). Good luck, Jim | |||||