From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "mascarm(at)mascari(dot)com" <mascarm(at)mascari(dot)com> |
Cc: | "'Tom Ivar Helbekkmo'" <tih(at)kpnQwest(dot)no>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, Mark Stosberg <mark(at)summersault(dot)com>, "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Re: behavior of ' = NULL' vs. MySQL vs. Standards |
Date: | 2001-06-08 16:53:16 |
Message-ID: | web-69313@davinci.ethosmedia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
Tom,
> Does Access only talk to Postgres via ODBC? (Seems plausible, but I
> don't know.)
Yes.
What about people copying-and-pasting queries generated
> by Access; is it even possible?
Yes, but MS Access uses some much non-standard SQL that "= Null" would
hardly be the only problem (try to build an UPDATE ... FROM in Access)
> I doubt that this'd really help much, in any case; it merely moves
> the
> necessary switch from the backend to ODBC.
Yes, but it does avoid cluttering up the PgSQL source with switches that
are only useful to a handful of users.
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-06-08 17:45:48 | Re: unlink large objects |
Previous Message | earthlink | 2001-06-08 16:49:13 | Implicit order-by in Postgresql? |
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan Bartlett | 2001-06-08 17:48:06 | Re: maximum number of rows in table - what about oid limits? |
Previous Message | Tom Lane | 2001-06-08 16:34:00 | Re: Getting row with id=max(id) |