From: | "Thomas T(dot) Veldhouse" <veldy(at)veldy(dot)net> |
---|---|
To: | "GH" <grasshacker(at)over-yonder(dot)net> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Problem with null timestamp fields |
Date: | 2001-06-28 03:29:17 |
Message-ID: | 007101c0ff82$831d70f0$0101a8c0@cascade |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes, that was it. It should have been more obvious had I looked closer. A
second pair of eyes are always helpful. Still, I am a bit amazed that the
database allows this (trailing or leading spaces in the column names).
Thanks for you help!
Tom Veldhouse
veldy(at)veldy(dot)net
----- Original Message -----
From: "GH" <grasshacker(at)over-yonder(dot)net>
To: "Thomas T. Veldhouse" <veldy(at)veldy(dot)net>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, June 27, 2001 10:03 PM
Subject: Re: [GENERAL] Problem with null timestamp fields
> > "ipaddr" character(15) NOT NULL,
> > "login_ts " timestamp with time zone,
> > "logout_ts " timestamp with time zone,
> >
> > PostgreSQL said: ERROR: Relation 'user_history' does not have attribute
> > 'login_ts'
> >
> > Obviously, I DO have login_ts. The field is nullable, so why the
headache?
>
> Obviously, you do not.
> You have 'login_ts '. Note the trailing space. Note the same for
> 'logout_ts'.
>
> QED
>
> gh
>
>
> >
> > Thanks in advance,
> >
> > Tom Veldhouse
> > veldy(at)veldy(dot)net
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
From | Date | Subject | |
---|---|---|---|
Next Message | エイエムエス | 2001-06-28 03:32:43 | installation error |
Previous Message | Jason Earl | 2001-06-28 03:15:55 | Re: Problem with null timestamp fields |