| From: | Byron Nikolaidis <byronn(at)insightdist(dot)com> |
|---|---|
| To: | Tim Bosinius <tim(at)bosinius(dot)de> |
| Cc: | "'pgsql-interfaces(at)postgreSQL(dot)org'" <pgsql-interfaces(at)postgreSQL(dot)org> |
| Subject: | Re: [INTERFACES] another ODBC/Access question.. |
| Date: | 1998-06-04 17:22:52 |
| Message-ID: | 3576D7EC.3AFE34ED@insightdist.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-06-04 17:30:04 | Re: [HACKERS] Re: libpgtcl bug (and symptomatic treatment) |
| Previous Message | Tom Lane | 1998-06-04 17:06:52 | Re: libpgtcl bug (and symptomatic treatment) |