RE: Update on Access 97 and = NULL

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> >> If the last parameter is set to SQL_NULL_DATA, then that means that the
> >> last parameter is NULL. That means that the query must be rewritten by
> >> the driver to "IS NULL" instead of "= NULL". Unfortunately, it
> *appears*
> >> our ODBC driver doesn't do that.
>
> This sounds like a plausible explanation.
>
> > You are right. I'd like to fix it.
> > When could we translate "= NULL" into "IS NULL" ?
>
[snip]
>
> But, taking that assumption as correct for the moment ---
>
> Given the choice of having the ODBC driver do this or letting the
> backend do it, I'd have to say that I prefer leaving it in the backend,
> because the ODBC driver just doesn't have enough understanding of SQL
> syntax to be able to get it right. It would take a major upgrade of the
> driver's SQL parser before I'd have any confidence in the translation
> being done correctly.
>

OK agreed.

> Yet ... in the long run that does need to happen, I think. Some day
> it'd be nice to see ODBC contain a full parser similar to ecpg's.

Hmm I fear the strong binding between the driver and the server.
Would the parser always be backward compatible ?

regards,
Hiroshi Inoue