[freetds] Request to map Sybase status code '3604' to SQLSTATE '01000'

[Yeung, Alinga]

Hi,

We use Sybase. We are porting our software to use Freetds. We come across a status code mapping from Sybase to Freetds that results in a behavioural discrepancy in our software.

In src/tds/mem.c, the Sybase status code '3604' is mapped to SQLSTATUS '23000'. This is causing our software to fail.

Sybase status code '3604' does not require any action to be taken. Our software treats the status code as informational/warning and does not take any action.

SQLSTATE '23000' indicates an error instead.

Locally we have changed mem.c to map the Sybase status code '3604' to '01000' which is a general warning, and our software works fine.

We would like to request that Sybase status code '3604' be mapped to an informational SQLSTATUS, e.g. '01000'.

Thank you.

Alinga

[Yeung, Alinga]

Hi,

We have not received any response to our request below. We are wondering if our request has been accepted or rejected. A response would be much appreciated.

In short, we are requesting that line 1469 in src/tds/mem.c (in freetds-0.91) be changed
from:
===
1469 SQLS_ENTRY(3604,"23000");
===
to:
===
1469 SQLS_ENTRY(3604,"01000");
===

Thank you in advance for your help.

Alinga
________________________________________
From: Yeung, Alinga
Sent: Wednesday, September 10, 2014 10:16 AM
To: freetds at lists.ibiblio.org
Subject: Request to map Sybase status code '3604' to SQLSTATE '01000'

Hi,

We use Sybase. We are porting our software to use Freetds. We come across a status code mapping from Sybase to Freetds that results in a behavioural discrepancy in our software.

In src/tds/mem.c, the Sybase status code '3604' is mapped to SQLSTATUS '23000'. This is causing our software to fail.

Sybase status code '3604' does not require any action to be taken. Our software treats the status code as informational/warning and does not take any action.

SQLSTATE '23000' indicates an error instead.

Locally we have changed mem.c to map the Sybase status code '3604' to '01000' which is a general warning, and our software works fine.

We would like to request that Sybase status code '3604' be mapped to an informational SQLSTATUS, e.g. '01000'.

Thank you.

Alinga

[Frediano Ziglio]

Hi,
sorry for no reply. Personally I would like to see what other
libraries does with this error.

Frediano

Post by Yeung, Alinga
Hi,
We have not received any response to our request below. We are wondering if our request has been accepted or rejected. A response would be much appreciated.
In short, we are requesting that line 1469 in src/tds/mem.c (in freetds-0.91) be changed
===
1469 SQLS_ENTRY(3604,"23000");
===
===
1469 SQLS_ENTRY(3604,"01000");
===
Thank you in advance for your help.
Alinga
________________________________________
From: Yeung, Alinga
Sent: Wednesday, September 10, 2014 10:16 AM
To: freetds at lists.ibiblio.org
Subject: Request to map Sybase status code '3604' to SQLSTATE '01000'
Hi,
We use Sybase. We are porting our software to use Freetds. We come across a status code mapping from Sybase to Freetds that results in a behavioural discrepancy in our software.
In src/tds/mem.c, the Sybase status code '3604' is mapped to SQLSTATUS '23000'. This is causing our software to fail.
Sybase status code '3604' does not require any action to be taken. Our software treats the status code as informational/warning and does not take any action.
SQLSTATE '23000' indicates an error instead.
Locally we have changed mem.c to map the Sybase status code '3604' to '01000' which is a general warning, and our software works fine.
We would like to request that Sybase status code '3604' be mapped to an informational SQLSTATUS, e.g. '01000'.
Thank you.
Alinga
_______________________________________________
FreeTDS mailing list
FreeTDS at lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds