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

Re: possible ODBC bug with '-infinity'

From: Richard Broersma Jr <rabroersma(at)yahoo(dot)com>
To: Greg Cocks <gcocks(at)stoller(dot)com>
Cc: Postgresql ODBC List <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: possible ODBC bug with '-infinity'
Date: 2007-11-30 18:12:18
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
--- On Fri, 11/30/07, Greg Cocks <gcocks(at)stoller(dot)com> wrote:

> Using a MS product? Is this *maybe* related to the same
> 'issue' with
> NULLs from PostgreSQL to MS products i.e., in the
> <postgresql.conf>
> file, turning 'transform_null_equals' to
> 'on'?
> Likely not, but thought I would put it out there...   :-)
> .. DEFAULT '-infinity', ...

I should probably clarify what I am seeing.

I have a table that has a time stamp field.  The timestamp fields have two special values in postgres:  
  'infinity' which implies '+infinity' 
  and '-infinity'

when I create a recordset of records that have the value 'infinity' in the timestamp field all is well.  The client side timestamp displays '9999-12-31 .... '.
However, when I try to create a recordset that has field that contains the '-infinity' values I get an error message.

Richard Broesma Jr.


pgsql-odbc by date

Next:From: Greg CocksDate: 2007-11-30 19:58:08
Subject: Can't get MS Access via ODBC (or MapServer) to 'see' the data unless the user is a 'super user'...
Previous:From: Richard Broersma JrDate: 2007-11-30 07:06:10
Subject: possible ODBC bug with '-infinity'

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