Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <fgp(at)phlo(dot)org>
Cc: <alex-goncharov(at)comcast(dot)net>,<cbbrowne(at)gmail(dot)com>, <mmoncure(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable
Date: 2011-10-10 11:25:07
Message-ID: 4E928FC30200002500041C77@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Florian Pflug wrote:
> On Oct9, 2011, at 14:20 , Kevin Grittner wrote:
>> Florian Pflug wrote:
>>
>>> Coming up with a reasonable algorithm isn't *that* hard.
>>
>> Agreed. Our shop has used a home-grown framework for over a decade
>> where we parse queries using ANTLR ( http://www.antlr.org/ ) and
>> we tracked this trough all expressions. There really weren't that
>> many situations where we had to punt.
>
> Sounds cool. What was your use-case for doing that?

Portability. That approach is what made the conversion to PostgreSQL
from the commercial product we were using quick and painless.

-Kevin

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2011-10-10 11:43:41 Re: pg_upgrade - add config directory setting
Previous Message Alex Goncharov 2011-10-10 11:09:55 Re: What is known about PostgreSQL HP-UX support?