From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sebastien FLAESCH <sf(at)4js(dot)com> |
Cc: | pgsql-interfaces(at)lists(dot)postgresql(dot)org |
Subject: | Re: Type scale returned by PQfmod() 65531 for time/timestamp output parameter? |
Date: | 2018-02-19 16:06:23 |
Message-ID: | 7047.1519056383@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Sebastien FLAESCH <sf(at)4js(dot)com> writes:
> On 02/16/2018 04:15 PM, Tom Lane wrote:
>> You could try running it through the typmodout function for the column's
>> datatype. I don't offhand know of any built-in types for which that would
>> be a really plausible typmod, though. Are you sure your client code isn't
>> mistakenly narrowing it to int16 somewhere?
> As I wrote in my initial mail, I do the following:
> #define VARHDRSZ 4
> int pgfmod = PQfmod(st->pgResult, i);
> int pgprec = (pgfmod >> 16);
> int pgscal = ((pgfmod - VARHDRSZ) & 0xffff);
> int pgleng = (pgfmod - VARHDRSZ);
That might --- I don't recall offhand --- be the right decoding for
the typmod of a column of type NUMERIC. It's certainly not right
for any other datatype. Also, you don't seem to be accounting for
the fact that negative typmod always means "no typmod specified".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sebastien FLAESCH | 2018-02-20 09:30:32 | Re: Type scale returned by PQfmod() 65531 for time/timestamp output parameter? |
Previous Message | Sebastien FLAESCH | 2018-02-19 11:16:45 | Re: Type scale returned by PQfmod() 65531 for time/timestamp output parameter? |