Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] By Passed Domain Constraints

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-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 :(


In response to

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2005-07-07 01:38:18
Subject: Mistake in latest plperl patch
Previous:From: Neil ConwayDate: 2005-07-07 01:00:36
Subject: Re: User's exception plpgsql

pgsql-interfaces by date

Next:From: Tim JacksonDate: 2005-07-08 00:58:28
Subject: C set return function differences on 8.0?
Previous:From: Robert PerryDate: 2005-07-06 17:36:00
Subject: Re: By Passed Domain Constraints

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group