Re: Automatic truncation of character values & casting to the type of a column type

From: Sam Mason <sam(at)samason(dot)me(dot)uk>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Automatic truncation of character values & casting to the type of a column type
Date: 2009-12-17 15:31:25
Message-ID: 20091217153125.GT5407@samason.me.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Dec 17, 2009 at 10:24:28AM -0500, Tom Lane wrote:
> Justin Bailey <jgbailey(at)gmail(dot)com> writes:
> > If s was automatically truncated, the insert would succeed, but it
> > fails with a "value too long" error.
>
> Oh, I thought the failure was the behavior you wanted. There's
> no automatic truncation here --- perhaps putting an exception
> block around it would be the way to go?

I think the OP wants to be able to use the "%TYPE" magic in more places
than the grammar currently accepts. For example, so that you can use it
in a CAST expression as per some of the examples.

Would using DOMAINs be a better alternative? It certainly works now.

--
Sam http://samason.me.uk/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2009-12-17 15:38:57 Re: Automatic truncation of character values & casting to the type of a column type
Previous Message Vincenzo Romano 2009-12-17 15:29:52 Re: Table Partitioning Advice Request