Terry Carlin wrote:
>
> I was wrong about the locate() function in the odbc driver. Thomas
> Lockhart pointed out that it mapped locate in the driver to strpos in
> postgres. This tweaked a memory. What happens with the locate() odbc
> function in the odbc test suite is that it calls locate wit
Tom Lane wrote:
>
> Thomas Lockhart <[EMAIL PROTECTED]> writes:
> > So now the question is what the ODBC standard says locate() should
> > return.
>
> Wups. I neglected to notice the disconnect between the message subject
> and body... but you are right, "locate" might not be the same as
> "posi
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> So now the question is what the ODBC standard says locate() should
> return.
Wups. I neglected to notice the disconnect between the message subject
and body... but you are right, "locate" might not be the same as
"position" :-(
> > While running an ODBC test suite against PostgreSQL 7.1, the test
> > software reported that the ODBC command locate("", "") failed.
> > It expected the result to be zero and it got a 1.
> Evidently your ODBC test suite hasn't read the spec. See 4.2.2.2 in
> either SQL92 or SQL99:
>
