|
Hey Martin, I don't know of any way to do what you're looking for in one step. I would rename the existing table, create the new one, etc., but indeed it will be a pain to put back all your referential integrity, indexes, views, and what-not. But the reason I replied is that a truly relational database by definition has no ordering of columns or rows, so I am really surprised that you care where in the table the column happens to fall, and yes, I'm curious why. > -----Original Message----- > From: McCallion, Martin [mailto:martin.mccallion@xxxxxxxxx] > > I need to change a table to add a column; this would be > straightforward > with the ALTER TABLE SQL statement, if the new column could go on the > end of the row. However, for reasons that I won't go into > unless people > are interested, the new column has to be inserted before some existing > columns; and the existing data has to be preserved. > NOTICE: This E-mail may contain confidential information. If you are not the addressee or the intended recipient please do not read this E-mail and please immediately delete this e-mail message and any attachments from your workstation or network mail system. If you are the addressee or the intended recipient and you save or print a copy of this E-mail, please place it in an appropriate file, depending on whether confidential information is contained in the message.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.