From: | Lewis Kapell <lkapell(at)setonhome(dot)org> |
---|---|
To: | Andre Rothe <phosco(at)gmx(dot)de> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Wrong column default values |
Date: | 2009-09-21 13:33:22 |
Message-ID: | 4AB780A2.7080307@setonhome.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
It's not really clear what problem you are trying to solve. You say
both column defaults should be NULL. Well, evidently they are.
NULL::timestamp without time zone
NULL::character varying
Those are NULL values. Are you confused by the information displayed
after the double colon? That's just Postgres' way of showing you what
the data type of the column is.
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
-------------------------------------------------------
For a free subscription to the Seton Home Study School monthly
electronic newsletter, send an e-mail to newsletter-sub(at)setonhome(dot)org
-------------------------------------------------------
Andre Rothe wrote:
> Hi,
>
> I have installed Postgres 8.3.8 on Fedora Linux. If I create a table,
> the default values will be set by the database to
>
> NULL::timestamp without time zone
>
> for a timezone column and to
>
> NULL::character varying
>
> for a varchar column. How I can prevent such a behaviour? Both column
> defaults should be NULL. I have read some posts about this point, it
> seems to be a problem of a so called "acts_as_tsearch plugin", but I'm
> not familiar enough with Postgres to know, what it means. Any other
> detailled solutions?
>
> Thanks
> Andre
>
From | Date | Subject | |
---|---|---|---|
Next Message | S Arvind | 2009-09-21 17:45:59 | Postgres restart |
Previous Message | Paweł Nieścioruk | 2009-09-21 09:08:57 | pg_hba.conf problem in PostgreSQL 8.4 (no-installer) |