On 29.11.24 20:30, Thomas Munro wrote:
On Fri, Nov 29, 2024 at 11:12 PM Thomas Munro <thomas.mu...@gmail.com> wrote:
I was thinking about that ECPG stuff: I bet real applications prefer
to use int64_t etc directly too instead of long, the worst type in C.
I wondered if the embedded SQL standard might know about that these
days (ECPGt_int64_t?), but I don't have the standard to hand. DB2's
embedded SQL seems to have a type sqlint64, but I didn't look too
closely and of course even if we wanted to do something like that as
an optional API option, that'd be a later change.
Interesting:
i) If “long long” is specified, then the <host parameter data type> of
HV is BIGINT.
ii) If “long” is specified, then the <host parameter data type> of HV is
INTEGER.
iii) If “short” is specified, then the <host parameter data type> of HV
is SMALLINT.
[...]
I suppose that makes sense.
BTW I forgot to mention earlier, I peeked at the source of gettext on
NetBSD and illumos, and both appear to handle those special
<inttypes.h> tokens when loading message catalogues.
Ah great, thanks for checking that.
