It's not as bad as I say, it's worse. Whatever, I did it ugly cause I just needed it to work. I'll spend a bit, and add a few comments, and fix a few things (Like looking up the rename stuff), and send it in.
Kev. ----- Original Message ----- From: "Jeff Clement" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 21, 2002 4:46 PM Subject: Re: (clug-talk) Well, Postgres it is. > Even if the code needs some work (and I'm sure it's not as bad as you say), > I'm certain other people would find it useful. One of my friends clients > was migrating away from SQL Server and hit similar problems. Some scripts > that helped out even if they needed "help". Who knows, it might spur > someone else into fixing it and converting it into a more general tool. > > Jeff > > --On Thursday, November 21, 2002 4:25 PM -0700 Kevin Anderson > <[EMAIL PROTECTED]> wrote: > > > > > So my script worked, except where MS SQL wanted a default of 'E' for a > > Float8 column. There were actually 3 columns I needed to do manually, 2 > > putting character values into numeric fields, and one when confused about > > a timezone issue. (The vendor is getting back to me on that one). > > Purdy successful, all in all. > > > > So here's my question. > > > > The utility I wrote was useful for me. It's ugly beyond words, and it's > > undoubtedly filled with errors, never mind having things that could just > > be done better. (For example, I forget how to rename a file, so I use a > > NASTY workaround. I open the bad filename for input, and the good > > filename for output, and the just input from one, and write into the > > other until it's done.) I have NEVER claimed to be a coder, and fear > > not, I'll stay the hell away from the kernel. > > So what do I do with this piece of useful junk I created? Should I send > > it to the Postgres guys for them to laugh at? Or hang my head in shame, > > and pretend it never existed. I'm certainly not putting my name on it, > > but there is the possibility that someone else might find a use for it. > > > > Kev. > > > >
