RE: Changing a table to have a new column before existing columns

Zak Metz wrote:

> 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.

Yes, good point.  The reason is that the table in question contains some
CLOBs (or they may be BLOBs, but they're definitely large objects).  The
database is accessed by a VB client and a Java server job.  Now, in the
past, our client application, at least, has had problems if the LOBs
were _not_ the last columns.  I don't remember the errors now, but they
definitely went away when we moved all the other columns to come before
the LOBs.  I don't really doubt that, with OS and driver improvements,
this would no longer be a problem; but it's a case of "once bitten,
twice shy".

Cheers,

Martin.

-- 
Martin McCallion
Senior Technical Consultant
Misys Wholesale Banking Systems
1 St George's Road, London, SW19 4DR, UK
T +44 (0)20 8486 1951
F +44 (0) 20 8947 3373
martin.mccallion@xxxxxxxxx
www.misys.com

This email and any attachments have been scanned for known viruses using
multiple scanners. We believe that this email and any attachments are
virus free, however the recipient must take full responsibility for
virus checking. This email message is intended for the named recipient
only. It may be privileged and/or confidential. If you are not the
intended named recipient of this email then you should not copy it or
use it for any purpose, nor disclose its contents to any other person.
You should contact the Misys Banking and Securities Division as shown
below so that we can take appropriate action at no cost to yourself. 

Misys Banking and Securities Division, 1 St George's Road, Wimbledon,
London, SW19 4DR, England. Email: banking.postmaster@xxxxxxxxxx Tel: +44
(0) 20 8879 1188 Fax: +44 (0) 20 8947 3373