I didn't stir up any responses to this post just over a year ago. The
issue has resurfaced at a customer site so I am still curious about
it. The following reproduces in Ingres 11.0 and as far back as Ingres
10.1 (which is as far as I could go).
---------------------- 8<--------------------------------------------
create table foo_tbl (keycol char(9) not null, good_stuff i1 not null)
\g
create table bar_tbl (keycol char(9) not null, other_stuff i1 not null)
\g
commit
\g
create view nice_view as select f.keycol
from foo_tbl f left join (select * from bar_tbl b ) x using (keycol)
\g
commit;
\g
-- this will fail with E_US16D5
alter table foo_tbl drop column good_stuff cascade;
\g
drop view nice_view;
\g
-- this will work
alter table foo_tbl drop column good_stuff cascade;
\g
---------------------- 8<--------------------------------------------
Thursday, September 26, 2019, 11:02:40 AM, you wrote:
This re Ingres SPARC SOLARIS Version II 11.0.0 (su9.us5/100)
* alter table medical drop column m_length cascade \g
Executing . . .
E_US16D5 Table specified no longer exists.
(Thu Sep 26 10:34:53 2019)
A bit of googling tells me this error has cropped up once or twice in
the past but none of the past cases seem relevant, e.g. there are no constraints involved.
Obviously I am wondering how to get past it, but my question here is why
I would ever get an error message that something "no longer" exists?
Surely to the DBMS a thing exists or it doesn't. Why the reference
to a past state of which it should be (or at least should seem to be) oblivious?
--Roy
_______________________________________________
Info-ingres mailing list
[email protected] https://lists.planetingres.org/mailman/listinfo/info-ingres
Roy Hann
Rational Commerce Ltd.
T +44 20 8691 2089
"Ingres development, tuning, and training experts"
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)