> > I'm thinking that I should put a 'SearchSysCacheCopy' where my
> @@ comment is
> > to retrieve the attribute by name, and then do a check to see if it's
> > dropped. Is that the best/fastest way of doing things? Seems
> unfortunate
> > to add a another cache lookup in every parsed query...
>
> I am still looking but perhaps you could supress dropped columns from
> getting into eref in the first place.
OK, that's done. I'm working on not allowing dropped columns in UPDATE
targets now.
Chris
