| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Perry <rlperry(at)lodestonetechnologies(dot)com>, pgsql-interfaces(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] By Passed Domain Constraints |
| Date: | 2005-07-07 01:23:26 |
| Message-ID: | 42CC840E.3030708@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
> You could work around this by explicitly specifying the parameter
> type as text or varchar or whatever the domain's base type is.
> I wonder though if we oughtn't change the backend so that the inferred
> type of a parameter symbol is never a domain, but the domain's base
> type. That would force the proper application of CoerceToDomain inside
> the constructed query parsetree.
Remember we have similar weirdness when returning domain types from
stored procs :(
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2005-07-07 01:38:18 | Mistake in latest plperl patch |
| Previous Message | Neil Conway | 2005-07-07 01:00:36 | Re: User's exception plpgsql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Jackson | 2005-07-08 00:58:28 | C set return function differences on 8.0? |
| Previous Message | Robert Perry | 2005-07-06 17:36:00 | Re: By Passed Domain Constraints |