The other discussion made me try this out:
> So the new dll did take out the delete column. I
> assume that if you do a drop column that it removes
> the associated index.
(Obviously 7.3.* is involved here...)
I did the following:
oms=# create table __temp1(field1 varchar(10), field2 varchar(10));
CREATE TABLE
oms=# create index __idx_temp1 on __temp1 (field1, field2);
CREATE INDEX
oms=# alter table __temp1 drop column field2;
ALTER TABLE
Note that the ALTER TABLE query succeeded *quietly* and did in fact drop
the index.
Is this intended behavior? Rather seems like it should refuse to drop
an indexed column, or at least refuse to drop a culumn that's a member
of a multi-culumm index and give notice when an index is dropped. I
think I'd opt for the never-drop-an-indexed-column approach.
Just an observation :-)
Glen Parker
glenebob@nwlink.com
