Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f58GrIE76769; Fri, 8 Jun 2001 12:53:18 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 69313; Fri, 08 Jun 2001 09:53:16 -0700 From: "Josh Berkus" Subject: Re: [HACKERS] Re: behavior of ' = NULL' vs. MySQL vs. Standards To: Tom Lane , "mascarm@mascari.com" Cc: "'Tom Ivar Helbekkmo'" , Stephan Szabo , Mark Stosberg , "pgsql-sql@postgresql.org" , "pgsql-hackers@postgresql.org" X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Fri, 08 Jun 2001 09:53:16 -0700 Message-ID: In-Reply-To: <9679.992012666@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200106/130 X-Sequence-Number: 3351 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@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco