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
Info-ingres@lists.planetingres.org https://lists.planetingres.org/mailman/listinfo/info-ingres
On Dec 15, 2020, at 7:27 AM, Roy Hann <roy.hann@rationalcommerce.com> wrote:[snip]
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).
* alter table medical drop column m_length cascade \g
Executing . . .
E_US16D5 Table specified no longer exists.
(Thu Sep 26 10:34:53 2019)
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?
This one turns out to be interesting. The dependency checker in QEF is mis-handling
the derived table in the view definition, as near as I can tell. Please open an
issue on this one.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 349 |
Nodes: | 16 (0 / 16) |
Uptime: | 142:38:46 |
Calls: | 7,613 |
Calls today: | 1 |
Files: | 12,790 |
Messages: | 5,684,458 |