From: | Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: User defined type without single quotes |
Date: | 2013-04-13 17:23:14 |
Message-ID: | CANs8QJbRKWLiJ7SSBF+P6W0ckw4TRbTQp-OJ-FDqueReJrbxuA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Thank you, Peter!
On Sat, Apr 13, 2013 at 10:06 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On Thu, 2013-04-04 at 19:50 -0300, Rodrigo Barboza wrote:
> > -- my_uint32 is my new type
> > CREATE TABLE test (a my_uin32);
> >
> > If I try to run this insert, postgres complain about the type:
> > INSERT INTO teste (a) VALUES (10);
> >
> > But this one works:
> > NSERT INTO teste (a) VALUES ('10'::my_uint);
> >
> > Is there a way to avoid the single quotes?
> >
> A constant like 10 is initially assigned one of the integer types (the
> exact rules are in the documentation). In order to be able to store
> that into a column of a custom type, you need to define a cast between
> the integer type and your type with at least assignment context.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2013-04-14 07:56:12 | Re: PGDATA confusion |
Previous Message | Peter Eisentraut | 2013-04-13 13:06:43 | Re: User defined type without single quotes |