Re: New Patch file for MS SQL autonumbers

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "John McCawley" <jmccawley(at)worleyco(dot)com>
Cc: "pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: New Patch file for MS SQL autonumbers
Date: 2002-06-17 20:45:37
Message-ID: D85C66DA59BA044EB96AB9683819CF610150FA@dogbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Thanks John, change commited, along with the Access fix you suggested.

Regards, Dave.

> -----Original Message-----
> From: John McCawley [mailto:jmccawley(at)worleyco(dot)com]
> Sent: 17 June 2002 16:58
> To: Dave Page
> Cc: pgadmin-hackers
> Subject: [pgadmin-hackers] New Patch file for MS SQL autonumbers
>
>
> Previously, my code used the contents of cnLocal.ConnectionString to
> determine whether we were migrating from a MS SQL database.
> This is how
> the access code was doing it, so I was mimicing that
> behavior. However,
> for whatever reason the case of the MSSQL string changed between CVS
> versions (That code hasn't changed, I have no idea what happened). I
> started to change the comparison to case insensitive, but instead
> changed the line to use the value of the option box to
> determine whether
> we're migrating from a MSSQL server. I believe that the Access code
> should also be modified in a similar manner. If the Access connect
> string is changed, more than likely whoever makes the change will not
> remember to also change the "if" that depends on that connect string.
>
> John
>
>
>

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2002-06-17 21:58:25 Re: New Patch file for MS SQL autonumbers
Previous Message John McCawley 2002-06-17 15:58:18 New Patch file for MS SQL autonumbers