townsendEbmud
Member²
I know this is esoteric, but what can I say...?
This has to do with TYPE evolution and inheritance (on Oracle 9.2.0.6). If I create type A with an attribute and procedure, then create type B under A (inheritance), B gets A's procedure. If I DESC A and DESC B the results are the same.
If I then alter type A drop the procedure with the cascade option, it should (and does) drop the procedure from B as well. However, if I DESC A and DESC B, the results correctly show the procedure as not being in A, but still show the procedure in B (incorrect).
I tried to reconnect to see if that made a difference but it did not. I then connected to SQL*Plus and DESC B returned the correct results (no procedure). So it appears to be a bug in PLSD's describe routine.
Not a big problem, but would be good to get this fixed as it can be confusing. Note: Just checked and the non-existent procedure appears in the browser pane as well.
Thanks.
This has to do with TYPE evolution and inheritance (on Oracle 9.2.0.6). If I create type A with an attribute and procedure, then create type B under A (inheritance), B gets A's procedure. If I DESC A and DESC B the results are the same.
If I then alter type A drop the procedure with the cascade option, it should (and does) drop the procedure from B as well. However, if I DESC A and DESC B, the results correctly show the procedure as not being in A, but still show the procedure in B (incorrect).
I tried to reconnect to see if that made a difference but it did not. I then connected to SQL*Plus and DESC B returned the correct results (no procedure). So it appears to be a bug in PLSD's describe routine.
Not a big problem, but would be good to get this fixed as it can be confusing. Note: Just checked and the non-existent procedure appears in the browser pane as well.
Thanks.
