From: | Kristis Makris <kristis(dot)makris(at)datasoft(dot)com> |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: 'infinity'::timestamp not translated correctly using |
Date: | 2002-03-29 16:38:24 |
Message-ID: | 1017419905.1679.5.camel@leonidas |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On Fri, 2002-03-29 at 09:29, Hiroshi Inoue wrote:
> > -----Original Message-----
> > From: Kristis Makris
> >
> > Hello,
> >
> > I'm issuing the following SQL statement through psql:
> >
> > mydb=# select 'infinity'::timestamp as reply;
> > reply
> > ----------
> > infinity
> > (1 row)
> >
> >
> > When I try to issue the same statement through VC++ in the following
> > piece of code I get back "2002-03-28 00:00:00". Is infinity somehow
> > effectively translated into now()::date || "00:00:00" by the driver?
>
> There's no concept of inifinity in the timestamp type of ODBC(and in
> many DBMSs).
Since postgres does allow it as a valid value of the date datatype,
shouldn't all postgres interfaces (jdbc/odbc, etc.) support it? If this
concept shouldn't be supported, then why is it by the backend?
> regards,
> Hiroshi Inoue
>
--
---------------------------------------------------------------------
Kristis Makris DataSoft Corporation
kristis(dot)makris(at)datasoft(dot)com http://www.datasoft.com
(480) 763-5777 x412
---------------------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2002-03-30 09:00:42 | Re: Difference between ODBCdirect Connection and Pass-through-query |
Previous Message | Hiroshi Inoue | 2002-03-29 16:29:13 | Re: 'infinity'::timestamp not translated correctly using ODBCv7.01.00.10 ? |