On Wed, Nov 25, 2009 at 1:02 PM, Merlin Moncure wrote:
>
> IMO, ('abc', 'def')::foo honestly should honor constraints on foo.
> This probably isn't controversial.
So who do we need to convince to make this happen? The things we could
do with this kick ass. Maybe the details of the file I linked a
Never fails. About 5 minutes after posting a URL, my cable modem
decides to get a new IP (having kept it since May).
http://71.228.226.35/~john/custom_data_types.sql
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.
On Tue, Nov 24, 2009 at 5:51 PM, Merlin Moncure wrote:
> On Tue, Nov 24, 2009 at 10:13 AM, John Oyler wrote:
>>>
>>> For now you have to put all checks in custom constructor functions.
>>>
>>> Scott
>>
>> I must not be looking in the rig
>
> John Oyler wrote:
>
>I can create one or more domains, and use those to create the
>>composite type from. But each domain can only be constrained in its
>>own value, I can't constrain element #1's value based on what element
>>#2's v
I can create one or more domains, and use those to create the
composite type from. But each domain can only be constrained in its
own value, I can't constrain element #1's value based on what element
#2's value is.
If I create a domain from a composite, it will complain with a "ERROR:
cdt.instant_
Yes. Sorry... brain fart, meant to type that instead.
John O.
On Sat, Nov 21, 2009 at 5:09 PM, Tom Lane wrote:
> John Oyler writes:
>> I receive this error message whenever I attempt to create a domain
>> from a custom type,
>
> By "custom type" do you mean a
I receive this error message whenever I attempt to create a domain
from a custom type, but Google comes up short on explanations. A few
mailing list messages touch on the subject, but nothing like the
details on just where the limits lay or why they are as they are (or
even if work is being done on
