Shulgin, Oleksandr wrote:
> On Jul 17, 2015 4:31 PM, "Andrew Dunstan" <[email protected]> wrote:
> > Incidentally, this doesn't look acceptable anyway:
> >>
> >> ! es->json_cxt.value(&es->json_cxt, num, JSONTYPE_NUMERIC,
> >> ! NUMERICOID, 1702 /* numeric_out */);
> >
> > We don't hardcode function oids elsewhere. So this is also something that
> > makes the patch unacceptable.
>
> Well, good to know (I believe I've asked about this in the first mail
> specifically).
>
> Is there any way a built-in function oid would change/differ on different
> server versions? What would be the recommended way to do this?
C'mon, that's a trivial problem. Just use getTypeOutputInfo();
numeric's OID is hardcoded as NUMERICOID.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
