Hello, All,

We're in the process of trying to migrate from IB 5.6 to IB 7.0, and, in
testing today, we identified a behaviour that seems... weird.

Assume you have a table defined as follows:

CREATE TABLE FOO (
FOO_ID INTEGER,
FOO_NAME VARCHAR(10)
)

CREATE ASCENDING UNIQUE INDEX FOO1 ON FOO(FOO_ID, FOO_NAME)

Now, it has been our experience in IB 5.6 that entering the command:

DROP TABLE FOO

will drop not only the table, but also all of the indexes associated with
this table. In our testing with IB 7.0, this does not seem to be the case:
we dropped table FOO, but index FOO1 was still present after dropping the
table.

So, is this a bug, a feature, or are we misreading how things are supposed
to work?

Thanks in advance for any assistance,

Brian