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

Re: BUG #5839: pgAdmin makes bad query for creating a table when default value specified

From: Aren Cambre <aren(at)arencambre(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5839: pgAdmin makes bad query for creating a table when default value specified
Date: 2011-01-15 04:12:01
Message-ID: AANLkTi=wqk1CgB-tqeSb1oMzpa26y8nRj_ySbNMKf7+c@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
This came from pgAdmin's *Default value* field. This field is supposed to
accept anything other than a string?

Aren

On Fri, Jan 14, 2011 at 9:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "Aren Cambre" <aren(at)arencambre(dot)com> writes:
> > Using pgAdmin 1.12.2, I just tried to create a table with a character
> > varying(18) column. I put "none" (without the quotes) in the "Default
> value"
> > field for that column.
>
> > When I press OK to create the table, I get a dialog saying:
> >   An error has occurred:
> >   ERROR: column "none" does not exist
>
> Well, yeah, that's what you'll get.  I don't see a bug here.
> If you want the literal string 'none' as default, you should put quotes
> around it.  If you don't want a default, you shouldn't put anything
> there.
>
>                        regards, tom lane
>

In response to

Responses

pgsql-bugs by date

Next:From: John R PierceDate: 2011-01-15 04:36:24
Subject: Re: BUG #5839: pgAdmin makes bad query for creating a table when default value specified
Previous:From: Tom LaneDate: 2011-01-15 03:51:47
Subject: Re: BUG #5839: pgAdmin makes bad query for creating a table when default value specified

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