SQLGetConnectAttr returns invalid value

This is a multi-part MIME message.

--=_reb-r5E3E9CB1-t4A78B5E1
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

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?

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)

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)

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.

Mike McDonald

This message is confidential to Prodea Systems, Inc unless otherwise indica=
ted
or apparent from its nature. This message is directed to the intended recip=
ient
only, who may be readily determined by the sender of this message and its=

contents. If the reader of this message is not the intended recipient, or a=
n
employee or agent responsible for delivering this message to the intended=

recipient:(a)any dissemination or copying of this message is strictly
prohibited; and(b)immediately notify the sender by return message and destr=
oy
any copies of this message in any form(electronic, paper or otherwise) that=
you
have.The delivery of this message and its information is neither intended t=
o be
nor constitutes a disclosure or waiver of any trade secrets, intellectual=

property, attorney work product, or attorney-client communications. The
authority of the individual sending this message to legally bind Prodea Sys=
tems
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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>

</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

Hi All,<o:p></o:p>

<o:p> </o:p>

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?<o:p></o:p>

<o:p> </o:p>

Here are Anoop’s originally modified
files:<o:p></o:p>

* pgapi30.c (rev 1.22 and 1.23)<o:p></o:p=
>

* connection.c (rev .1.106)<o:p></o:p></s=
pan>

* connection.h (rev 1.65)<o:p></o:p></spa=
n>

<o:p> </o:p>

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:<o:p></o:p>

* pgapi30.c (rev 1.29)<o:p></o:p><=
/p>

* connection.c (rev 1.134)<o:p></o:p></sp=
an>

* connection.h (rev 1.69)<o:p></o:p></spa=
n>

<o:p> </o:p>

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=
..<o:p></o:p>

<o:p> </o:p>

Mike McDonald<o:p></o:p>

<o:p> </o:p>

</div>

</body>

</html>

<pre>

This message is confidential to Prodea Systems, Inc unless otherwise indica=
ted
or apparent from its nature. This message is directed to the intended recip=
ient
only, who may be readily determined by the sender of this message and its=

contents. If the reader of this message is not the intended recipient, or a=
n
employee or agent responsible for delivering this message to the intended=

recipient:(a)any dissemination or copying of this message is strictly
prohibited; and(b)immediately notify the sender by return message and destr=
oy
any copies of this message in any form(electronic, paper or otherwise) that=
you
have.The delivery of this message and its information is neither intended t=
o be
nor constitutes a disclosure or waiver of any trade secrets, intellectual=

property, attorney work product, or attorney-client communications. The
authority of the individual sending this message to legally bind Prodea Sys=
tems
is neither apparent nor implied,and must be independently verified.</pre>

--=_reb-r5E3E9CB1-t4A78B5E1--