| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Giovani Garcia <giovani(dot)garcia(at)protonmail(dot)com> |
| Cc: | "pgsql-interfaces(at)lists(dot)postgresql(dot)org" <pgsql-interfaces(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Doubt regarding query parameter metadata |
| Date: | 2021-04-01 14:14:20 |
| Message-ID: | 3396840.1617286460@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Giovani Garcia <giovani(dot)garcia(at)protonmail(dot)com> writes:
> The issue I'm finding is that the Oid returned for a VARCHAR column is TEXTOID (25) instead of VARCHAROID (1043).
This isn't hugely surprising in general. varchar has no operations
of its own; PG treats it as sort of a domain over text. So if you
do anything at all to a varchar column, it'd be quite likely for
the column to be implicitly coerced to text within the query.
> Now, when I run the following program (simplified for brevity),
> "SELECT key FROM oid_test WHERE value = $1",
Is that the *exact* query you're issuing? I don't see anything
in that that would cause a coercion, but maybe you left out some
relevant detail.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Giovani Garcia | 2021-04-01 15:30:05 | Re: Doubt regarding query parameter metadata |
| Previous Message | Giovani Garcia | 2021-04-01 03:33:40 | Doubt regarding query parameter metadata |