Re: Reintegrating years of local FreeTDS changes

That's not good (or intentional!), but I'm not sure why that would be;
that combination still works for me:

  $ TDSVER=7.3 ./src/apps/tsql -o v -H MSDEV1 -p 1433 -U DBAPI_test
  Password:
  locale is "LC_CTYPE=en_US.UTF-8;LC_NUMERIC=en_US.UTF-8;LC_TIME=en_US.UTF-8;LC_COLLATE=C;LC_MONETARY=en_US.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=en_US.UTF-8;LC_ADDRESS=en_US.UTF-8;LC_TELEPHONE=en_US.UTF-8;LC_MEASUREMENT=en_US.UTF-8;LC_IDENTIFICATION=en_US.UTF-8"
  locale charset is "UTF-8"
  using default charset "UTF-8"
  1> SELECT @@version
  2> go
  
  using TDS version 7.3
  Microsoft SQL Server 2014 (SP2-GDR) (KB4057120) - 12.0.5214.6 (X64)
  	Jan  9 2018 15:03:12
  	Copyright (c) Microsoft Corporation
  	Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
  
  (1 row affected)
  using TDS version 7.3

Would you mind bisecting to determine which commit broke this
combination for you?

-- Aaron Ucko <ucko at ncbi>, NCBI C++ Toolkit core development group

Sebastien FLAESCH <[email protected]> writes:

> I could execute our QA tests with SQL Server 2016 and 2017 without detecting
> any regression, by using the "master" branch.
>
> But it fails to connect to SQL Server 2014 (12.0).
>
> Is there some limitation regarding the supported SQL Server version?
>
> ODBCINI:
>
> [ftm_msvtest1_ida_utf8]
> Description     = SQL Server 2014
> Server          = ida
> Database        = msvtest1
> Port            = 1681
> TDS_Version     = 7.3
> ClientCharset   = UTF-8
>
>
> Seb