SQLGetConnectAttr returns invalid value
am 05.08.2009 00:18:52 von Mike McDonaldThis is a multi-part MIME message.
--=_reb-r5E3E9CB1-t4A78B5E1
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi All,
=20
I have a question regarding some changes that Anoop Kumar submitted
almost 4 years ago. The changes were a "fix for making the
SQLGetConnectAttr API work with SQL_ATTR_CONNECTION_DEAD attribute."
However, the changes are now not part of the current release. Why were
they removed?
=20
Here are Anoop's originally modified files:
* pgapi30.c (rev 1.22 and 1.23)
* connection.c (rev .1.106)
* connection.h (rev 1.65)
=20
His code was removed when Dave Page commited "changed files from the
[release 7.03] enhanced branch" to the main branch in the following
revisions:
* pgapi30.c (rev 1.29)
* connection.c (rev 1.134)
* connection.h (rev 1.69)
=20
In short, the SQLGetConnectAttr() function no longer returns an accurate
value for the CONNECTION_DEAD attribute. Was this simply a bad merge,
or was it removed on purpose? Thanks for the help.
=20
Mike McDonald
=20
This message is confidential to Prodea Systems, Inc unless otherwise indica=
ted=20
or apparent from its nature. This message is directed to the intended recip=
ient=20
only, who may be readily determined by the sender of this message and its=
=20
contents. If the reader of this message is not the intended recipient, or a=
n=20
employee or agent responsible for delivering this message to the intended=
=20
recipient:(a)any dissemination or copying of this message is strictly=20
prohibited; and(b)immediately notify the sender by return message and destr=
oy=20
any copies of this message in any form(electronic, paper or otherwise) that=
you=20
have.The delivery of this message and its information is neither intended t=
o be=20
nor constitutes a disclosure or waiver of any trade secrets, intellectual=
=20
property, attorney work product, or attorney-client communications. The=20
authority of the individual sending this message to legally bind Prodea Sys=
tems =20
is neither apparent nor implied,and must be independently verified.
--=_reb-r5E3E9CB1-t4A78B5E1
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
:10.0pt;
font-family:"Arial","sans-serif"'>Hi All,
:10.0pt;
font-family:"Arial","sans-serif"'>
:10.0pt;
font-family:"Arial","sans-serif"'>I have a question regarding some changes =
that
Anoop Kumar submitted almost 4 years ago. The changes were a "fi=
x for
making the SQLGetConnectAttr API work with SQL_ATTR_CONNECTION_DEAD
attribute." However, the changes are now not part of the current
release. Why were they removed?
:10.0pt;
font-family:"Arial","sans-serif"'>
:10.0pt;
font-family:"Arial","sans-serif"'>Here are Anoop’s originally modified
files:
:10.0pt;
font-family:"Arial","sans-serif"'>* pgapi30.c (rev 1.22 and 1.23)
:10.0pt;
font-family:"Arial","sans-serif"'>* connection.c (rev .1.106)
:10.0pt;
font-family:"Arial","sans-serif"'>* connection.h (rev 1.65)
:10.0pt;
font-family:"Arial","sans-serif"'>
:10.0pt;
font-family:"Arial","sans-serif"'>His code was removed when Dave Page commi=
ted
"changed files from the [release 7.03] enhanced branch" to the ma=
in
branch in the following revisions:
:10.0pt;
font-family:"Arial","sans-serif"'>* pgapi30.c (rev 1.29)
/p>
:10.0pt;
font-family:"Arial","sans-serif"'>* connection.c (rev 1.134)
:10.0pt;
font-family:"Arial","sans-serif"'>* connection.h (rev 1.69)
:10.0pt;
font-family:"Arial","sans-serif"'>
:10.0pt;
font-family:"Arial","sans-serif"'>In short, the SQLGetConnectAttr() functio=
n no
longer returns an accurate value for the CONNECTION_DEAD attribute. W=
as this
simply a bad merge, or was it removed on purpose? Thanks for the help=
..
:10.0pt;
font-family:"Arial","sans-serif"'>
:10.0pt;
font-family:"Arial","sans-serif"'>Mike McDonald
This message is confidential to Prodea Systems, Inc unless otherwise indica=
ted=20
or apparent from its nature. This message is directed to the intended recip=
ient=20
only, who may be readily determined by the sender of this message and its=
=20
contents. If the reader of this message is not the intended recipient, or a=
n=20
employee or agent responsible for delivering this message to the intended=
=20
recipient:(a)any dissemination or copying of this message is strictly=20
prohibited; and(b)immediately notify the sender by return message and destr=
oy=20
any copies of this message in any form(electronic, paper or otherwise) that=
you=20
have.The delivery of this message and its information is neither intended t=
o be=20
nor constitutes a disclosure or waiver of any trade secrets, intellectual=
=20
property, attorney work product, or attorney-client communications. The=20
authority of the individual sending this message to legally bind Prodea Sys=
tems =20
is neither apparent nor implied,and must be independently verified.
--=_reb-r5E3E9CB1-t4A78B5E1--