From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
cc: Mark Wong <markwkm@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: real/float example for testlibpq3
In-reply-to: <CAExHW5tm1FyoLZXdTjdrfRO7ObuoL_p2krc65C5s8D3eWFB50g@mail.gmail.com>
References: <Yhf70G9OYIKueYZi@workstation-mark-wong> <CAExHW5tm1FyoLZXdTjdrfRO7ObuoL_p2krc65C5s8D3eWFB50g@mail.gmail.com>
Comments: In-reply-to Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
	message dated "Mon, 28 Feb 2022 18:33:30 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2511608.1646061540.1@sss.pgh.pa.us>
Date: Mon, 28 Feb 2022 10:19:00 -0500
Message-ID: <2511609.1646061540@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/2511609.1646061540%40sss.pgh.pa.us>
Precedence: bulk

Ashutosh Bapat <ashutosh.bapat.oss@gmail.com> writes:
> I am wondering whether we should provide PQgetfloatvalue() which does
> what that example shows but transparently. It will return a float
> value of the given field instead of char *.

I'm against that, precisely because ...

> That will standardize the
> way to fetch real typed values in libpq. That leads to the next
> question. Do we need to introduce different PQget*value() for standard
> C/SQL data types.

... I do not want to go here.  Where would you stop?  How would you
deal with cross-machine inconsistencies in integer widths?

			regards, tom lane