Re: [General] pg_atoi problem with 7.3.2

From: nolan(at)celery(dot)tssi(dot)com
To: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane)
Cc: ler(at)lerctr(dot)org (Larry Rosenman), pgsql-general(at)postgresql(dot)org (pgsql general list)
Subject: Re: [General] pg_atoi problem with 7.3.2
Date: 2003-05-20 08:10:09
Message-ID: 20030520081009.256.qmail@celery.tssi.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> But that change was present in 7.3 (and 7.3.1). Right offhand I see
> nothing in the 7.3.2 change list that would explain the difference of
> behavior Mike is reporting between 7.3.1 and 7.3.2.

Um, never mind. :sigh:

Though I was unaware of the pg_atoi change, I came up with a patch for
this problem back in January because some of the files I'm converting
from have some zero length numeric fields in it that dBase and Access
don't complain about. Those files were having some other problems
that I thought might have been related to the zero length field issue.

Apparently I didn't get that patch compiled on the system I am running
7.3.2 on when I built it last month, though I have the modified source
there. After I compile the modified source, it works on that system.

I must have gotten sidetracked before I got it compiled that night.
Can I crawl under a rock and hide somewhere?
--
Mike Nolan

In response to

Browse pgsql-general by date

  From Date Subject
Next Message javier garcia - CEBAS 2003-05-20 09:04:02 PRIMARY KEYS
Previous Message shreedhar 2003-05-20 06:34:34 How to get required space between field names