Bug in ODBC driver

Started by Jan Wieckover 24 years ago2 messages
#1Jan Wieck
JanWieck@Yahoo.com

Guys,

while analyzing some stuff I came across something that looks
like a bug in the ODBC driver to me. I'm by far not the ODBC
user I should be to fix it, so could someone else please take
another look?

The symptom is when the driver is in AUTOCOMMIT=OFF, closing
the last used curser issues an END, thereby committing the
transaction. It happens in odbc/qresult.c line 320 and the
code looks pretty much like ignoring the autocommit flag.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

#2Hiroshi Inoue
Inoue@tpf.co.jp
In reply to: Jan Wieck (#1)
Re: [HACKERS] Bug in ODBC driver

Jan Wieck wrote:

Guys,

while analyzing some stuff I came across something that looks
like a bug in the ODBC driver to me. I'm by far not the ODBC
user I should be to fix it, so could someone else please take
another look?

The symptom is when the driver is in AUTOCOMMIT=OFF, closing
the last used curser issues an END, thereby committing the
transaction. It happens in odbc/qresult.c line 320 and the
code looks pretty much like ignoring the autocommit flag.

You seem to be right.
I would fix it.

regards,
Hiroshi Inoue