Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org (8.8.8/8.7.5) with ESMTP id NAA07808 for ; Thu, 4 Jun 1998 13:45:53 -0400 (EDT) Received: from insightdist.com (nobody@localhost) by u1.abs.net (8.9.0/8.9.0) with UUCP id NAA19968 for pgsql-interfaces@postgreSQL.org; Thu, 4 Jun 1998 13:29:28 -0400 (EDT) X-Authentication-Warning: u1.abs.net: nobody set sender to insightdist.com!byronn using -f Received: from ceodev by insightdist.com (AIX 3.2/UCB 5.64/4.03) id AA38945; Thu, 4 Jun 1998 13:20:08 -0400 Received: from [3.0.0.50] by ceodev (AIX 4.1/UCB 5.64/4.03) id AA77408; Thu, 4 Jun 1998 13:20:08 -0400 Message-Id: <3576D7EC.3AFE34ED@insightdist.com> Date: Thu, 04 Jun 1998 13:22:52 -0400 From: Byron Nikolaidis X-Mailer: Mozilla 4.05 [en] (Win95; I) Mime-Version: 1.0 To: Tim Bosinius Cc: "'pgsql-interfaces@postgreSQL.org'" Subject: Re: [INTERFACES] another ODBC/Access question.. References: <01BD8FE8.0612EC50.tim@bosinius.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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