Aidan Mountford wrote:
>
> I had a few issues with boolean handling in ODBC driver.
>
> 1) When a row is retrieved, and then a SQL_FETCH_FIRST is issued, the check
> in convert.c
> does not consider the fact that the value in the field has been altered to
> be a '1' if the
> backend handed it a 't'. The net result being that the first row on any
> subsequent queries
> has all it's boolean set to 0.
>
You seem to be right.
I would commit it as soon as I am able to have a cvs access(
I hope it would be before 7.2 release).
> 2) I had issues with some utilities that, when casting from string to
> boolean, and having
> the global 'bools as char' set, require that -1 = True, and 0 = false.
>
Hmm I don't understand this.
Please explain more in detail.
regards,
Hiroshi Inoue