Hi,
I was using ODBC with protocol set as 6.4, but the problem was when an error
occurs: the same code was returned for all kind of errors. After some tests,
I changed to protocol 7.4 and the problem was solved.
My question is: what could have changed with the use of protocol 7.4,
besides the error code? I've already done some tests on the statements, but
I'd like to know what to care for.

Thanks in advance,

Renato.


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Renato Gondim wrote:
> Hi,
> I was using ODBC with protocol set as 6.4, but the problem was when an error
> occurs: the same code was returned for all kind of errors. After some tests,
> I changed to protocol 7.4 and the problem was solved.
> My question is: what could have changed with the use of protocol 7.4,
> besides the error code? I've already done some tests on the statements, but
> I'd like to know what to care for.
>

By checking 7.4+ the driver would use FE/BE Protocol 3.

regards,
Hiroshi Inoue

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match