| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Cc: | Mark Wong <markwkm(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: real/float example for testlibpq3 |
| Date: | 2022-02-28 15:19:00 |
| Message-ID: | 2511609.1646061540@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2022-02-28 15:33:07 | Use "WAL segment" instead of "log segment" consistently in user-facing messages |
| Previous Message | Tom Lane | 2022-02-28 15:12:42 | Re: psql: Make SSL info display more compact |