Re: Warning: dbexport can't handle a column named current

David Williams wrote: > > In article <34858F4F.4CE49902@garpac.com>, Jacob Salomon > <jake@garpac.com> writes > >Any comments? Known bugs? Flames at my group for using the column > >name "current" in the first place? That last one would be unfair, > >since it > Monster flame from me! Don't be so daft! > > is not a reserved word. I claim this is a bug in dbexport, > > seldom encountered because most people have the good sense to be > > paranoid about formerly reserved words. :-)) > > What happens in isql/dbaccess when you try to select that column. I > claim it is an engine bug for allowing you to create it. I almost agree - perhaps the engine should not have allowed us to create the column with the same name as any built-in function. However, what happens when informix enhances the engine with a new built-in function everyone is clamoring for and it happens to have the same name as a column I already have? Will my SELECT statements now go bananas? YUP! The only real solution - and it is mostly painless - is to change the RENAME COLUMN the table and get it out of the way. Update the application programs - well, it's not always straightforward and not as painless, but it can be done. A massive grep would help. -- -- Jake (Pass the painkillers, bartender!) +------------------------------------------------------------+ | The expedient performance of a task with excessive concern | | regarding its duration-to-completion engenders a virtual | | certainty of diminished benefit therefrom. | | -- Benjamin Franklin (but he said it in 3 words) | +------------------------------------------------------------+