From: Byron Nikolaidis <byronn@insightdist.com>
To: Tim Bosinius <tim@bosinius.de>
Cc: 'pgsql-interfaces@postgreSQL.org' <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] another ODBC/Access question..
Date: Thu, 04 Jun 1998 13:22:52 -0400
Message-ID: <3576D7EC.3AFE34ED@insightdist.com> (raw)
References: <01BD8FE8.0612EC50.tim@bosinius.de>
Tim Bosinius wrote:
> When connecting Access97 to a postgreSQL datasource with ODBC
> the pg_attribute.attnuotnull is not queried and therefore not set
> in Access.
>
Currently, the driver just returns "everything is nullable". It used to vary
based on datatypes, but since most datatypes can handle nulls, that wasn't
very good.
I think it would make a good addition to the driver to handle nulls based on
the column attribute as you suggest. For Access, which uses SQLColumns to
determine this fact, this will work great. However, other applications that
use SQLDescribeCol or SQLColAttributes will still get only the datatype
nullability since there really is no easy way to get this kind of information
given only a result set from the backend.
I will add this in the next release.
Byron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: byronn@insightdist.com, tim@bosinius.de
Subject: Re: [INTERFACES] another ODBC/Access question..
In-Reply-To: <3576D7EC.3AFE34ED@insightdist.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox