| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4391.1 | | NOVA::SMITHI | Don't understate or underestimate Rdb! | Thu Aug 15 1996 16:38 | 6 |
| 4391.2 | log showing query outline + error | M5::GHODSON | | Fri Aug 16 1996 12:12 | 206 |
| 4391.3 | | NOVA::SMITHI | Don't understate or underestimate Rdb! | Fri Aug 16 1996 12:23 | 6 |
| 4391.4 | Source location | M5::GHODSON | | Fri Aug 16 1996 17:15 | 33 |
| 4391.5 | Is the file spec correct? | BOUVS::OAKEY | I'll take Clueless for $500, Alex | Sun Aug 18 1996 20:13 | 12 |
| 4391.6 | my mistake.. | M5::GHODSON | | Wed Aug 21 1996 10:36 | 12 |
| 4391.7 | Still a problem with Rdb 7.0 | M5::GHODSON | | Wed Nov 27 1996 11:03 | 2 |
| 4391.8 | | NOVA::SMITHI | Don't understate or underestimate Rdb! | Wed Nov 27 1996 11:09 | 5 |
| 4391.9 | fyi: problem found and fixed | NOVA::SMITHI | Don't understate or underestimate Rdb! | Fri May 30 1997 00:13 | 20 |
| Prior versions of Rdb generated incorrect query outlines for
multistatement procedures (this includes stored procedures, stored
functions and anonomous compound statements) which contained nested
queries.
The order of the queries in the query outline represents a flattened
tree structure that represents the complex execution profile of the
compound statement. When extracting this tree structure Rdb was
generating an order related to the top down structure of the
procedure, however, the optimizer requires a bottom up representation
of the optimization phase.
This means that query outlines generated for any procedure with nested
statements can not be used by the query optimizer. A work around is
to edit the generated query outline and move the query in the outline
to the correct position.
This problem is corrected in the next ECO to Rdb V6.1A and Rdb7. The
query outline now correctly represents the query optimizers query
tree.
|