Skip to Content.
Sympa Menu

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

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Yeung, Alinga" <Alinga.Yeung AT nrc-cnrc.gc.ca>
  • To: "freetds AT lists.ibiblio.org" <freetds AT lists.ibiblio.org>
  • Subject: [freetds] Request to map Sybase status code '3604' to SQLSTATE '01000'
  • Date: Wed, 10 Sep 2014 10:16:29 -0700

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] Request to map Sybase status code '3604' to SQLSTATE '01000', Yeung, Alinga, 09/10/2014

Archive powered by MHonArc 2.6.24.

Top of Page