From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Perry <rlperry@lodestonetechnologies.com>
Cc: pgsql-interfaces@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] By Passed Domain Constraints
Date: Thu, 07 Jul 2005 09:23:26 +0800
Message-ID: <42CC840E.3030708@familyhealth.com.au> (raw)
In-Reply-To: <27039.1120665958@sss.pgh.pa.us>
References: <61C4410A-F2CE-49E9-92BA-1BDF89818DAA@lodestonetechnologies.com>
<26103.1120660537@sss.pgh.pa.us>
<B37006A8-8E96-4E45-B01F-11BA87DF383F@lodestonetechnologies.com>
<27039.1120665958@sss.pgh.pa.us>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: chriskl@familyhealth.com.au, tgl@sss.pgh.pa.us, rlperry@lodestonetechnologies.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] By Passed Domain Constraints
In-Reply-To: <42CC840E.3030708@familyhealth.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox