gmane.comp.db.tds.freetds archive

6979 archived articles, newest first (page 1 of 70). Latest articles →

Re: ODBC develoment
Wed, 4 Dec 2019 10:50:26 +0100
"wgloger" <[email protected]> • #16978
Re: ODBC develoment
Sat, 7 Dec 2019 11:25:35 +0000
Frediano Ziglio <[email protected]> • #16977
ODBC develoment
Mon, 2 Dec 2019 15:40:38 -0500
Igor Korot <[email protected]> • #16976
Discontinuing the pymssql Project
Wed, 6 Nov 2019 14:48:33 -0500
Randy Syring <randy-+PLZm/s06Zpa7S/[email protected]> • #16975
Re: Latest freetds version upgrade
Fri, 18 Oct 2019 10:46:29 +0100
Frediano Ziglio <[email protected]> • #16974
Latest freetds version upgrade
Wed, 16 Oct 2019 12:38:00 +0000 (UTC)
Panos Stavroulis via FreeTDS <[email protected]> • #16973
Upgrade to latest freetds version
Wed, 16 Oct 2019 10:03:05 +0000 (UTC)
Panos Stavroulis via FreeTDS <[email protected]> • #16972
Re: Issues authenticating with freebcp
Tue, 18 Jun 2019 09:39:45 +0100
Frediano Ziglio <[email protected]> • #16971
Issues authenticating with freebcp
Tue, 28 May 2019 09:10:05 +0200
"Axel Vestin" <[email protected]> • #16970
(no subject)
Wed, 5 Jun 2019 15:50:56 -0400
Randy Syring <[email protected]> • #16969
Re: Support for SQL Server 2019
Fri, 05 Apr 2019 18:30:05 +0200
"Peter van Dijk" <[email protected]> • #16968
Re: FreeTDS 1.1 is out!
Thu, 14 Mar 2019 11:44:54 +0100
Sebastien FLAESCH <[email protected]> • #16967
FreeTDS 1.1 is out!
Thu, 14 Mar 2019 08:23:23 +0000
Frediano Ziglio <[email protected]> • #16966
Solved: Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication.
Mon, 4 Mar 2019 14:44:27 +0000
"Tille, Andreas" <[email protected]> • #16965
Re: SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Thu, 28 Feb 2019 18:03:35 +0000
Frediano Ziglio <[email protected]> • #16964
Re: SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Thu, 28 Feb 2019 14:22:18 +0000
Frediano Ziglio <[email protected]> • #16963
Re: SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Thu, 28 Feb 2019 15:19:11 +0100
Sebastien FLAESCH <[email protected]> • #16962
Re: SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Thu, 28 Feb 2019 10:56:03 +0000
Frediano Ziglio <[email protected]> • #16961
Re: SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Thu, 28 Feb 2019 11:50:09 +0100
Sebastien FLAESCH <[email protected]> • #16960
Re: SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Wed, 27 Feb 2019 10:32:28 -0500
Craig Jackson <[email protected]> • #16959
Re: SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Wed, 27 Feb 2019 16:27:40 +0100
Sebastien FLAESCH <[email protected]> • #16958
Re: SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Wed, 27 Feb 2019 14:08:16 +0000
Frediano Ziglio <[email protected]> • #16957
Re: Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication.
Wed, 27 Feb 2019 08:50:10 +0000
Frediano Ziglio <[email protected]> • #16956
Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication.
Tue, 26 Feb 2019 15:52:04 +0000
"Tille, Andreas" <[email protected]> • #16955
SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Thu, 21 Feb 2019 15:16:57 +0100
Sebastien FLAESCH <[email protected]> • #16954
Re: FreeTDS 1.1 Release Candidate 3
Mon, 25 Feb 2019 09:15:33 -0600
Mike Jetzer <[email protected]> • #16953
Re: SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Fri, 22 Feb 2019 10:15:37 +0000
Frediano Ziglio <[email protected]> • #16952
SQL Server 2019: CHAR(N) using UTF-8 is seen as SQL_NVARCHAR by SQLDescribeCol()
Thu, 21 Feb 2019 15:54:05 +0100
Sebastien FLAESCH <[email protected]> • #16951
Re: FreeTDS 1.1 Release Candidate 3
Thu, 21 Feb 2019 11:07:05 +0100
Sebastien FLAESCH <[email protected]> • #16950
Re: FreeTDS 1.1 Release Candidate 3
Thu, 21 Feb 2019 10:24:27 +0100
Sebastien FLAESCH <[email protected]> • #16949
FreeTDS 1.1 Release Candidate 3
Thu, 21 Feb 2019 08:42:27 +0000
Frediano Ziglio <[email protected]> • #16948
Re: FreeTDS 1.1 Release Candidate 2 - compiler warnings
Tue, 19 Feb 2019 08:32:32 -0600
Mike Jetzer <[email protected]> • #16947
Re: FreeTDS 1.1 Release Candidate 2 - compiler warnings
Wed, 20 Feb 2019 09:47:26 +0000
Frediano Ziglio <[email protected]> • #16946
Support for SQL Server 2019
Tue, 19 Feb 2019 18:51:32 +0100
Sebastien FLAESCH <[email protected]> • #16945
Re: FreeTDS 1.1 Release Candidate 2 - compiler warnings
Tue, 19 Feb 2019 08:28:15 +0000
Frediano Ziglio <[email protected]> • #16944
Re: FreeTDS 1.1 Release Candidate 2 - compiler warnings
Fri, 15 Feb 2019 14:35:34 -0600
Mike Jetzer <[email protected]> • #16943
Re: FreeTDS 1.1 Release Candidate 2 - compiler warnings
Fri, 15 Feb 2019 10:20:39 +0000
Frediano Ziglio <[email protected]> • #16942
Re: FreeTDS 1.1 Release Candidate 2
Wed, 13 Feb 2019 11:45:07 +0100
Sebastien FLAESCH <[email protected]> • #16941
Re: FreeTDS 1.1 Release Candidate 2 - compiler warnings
Mon, 11 Feb 2019 09:20:02 -0600
Mike Jetzer <[email protected]> • #16940
Re: FreeTDS 1.1 Release Candidate 2 - compiler warnings
Mon, 11 Feb 2019 10:17:48 +0100
Sebastien FLAESCH <[email protected]> • #16939
FreeTDS 1.1 Release Candidate 2
Sat, 9 Feb 2019 18:58:32 +0000
Frediano Ziglio <[email protected]> • #16938
Re: FreeTDS 1.1 Release Candidate 1
Tue, 05 Feb 2019 12:41:22 +0000
[email protected] • #16937
Re: FreeTDS 1.1 Release Candidate 1
Tue, 5 Feb 2019 11:39:55 +0000
Frediano Ziglio <[email protected]> • #16936
Re: FreeTDS 1.1 Release Candidate 1 - testing
Tue, 5 Feb 2019 10:29:29 +0100
Sebastien FLAESCH <[email protected]> • #16935
Re: FreeTDS 1.1 Release Candidate 1
Tue, 05 Feb 2019 09:17:35 +0000
[email protected] • #16934
Re: FreeTDS 1.1 Release Candidate 1 - compilation warnings
Tue, 5 Feb 2019 09:39:15 +0100
Sebastien FLAESCH <[email protected]> • #16933
Re: FreeTDS 1.1 Release Candidate 1
Tue, 5 Feb 2019 07:43:07 +0000
Frediano Ziglio <[email protected]> • #16932
Re: FreeTDS 1.1 Release Candidate 1
Tue, 05 Feb 2019 04:52:53 +0100
Fredy Paquet <[email protected]> • #16931
Re: FreeTDS 1.1 Release Candidate 1
Tue, 5 Feb 2019 04:30:29 +0100 (GMT+01:00)
<[email protected]> • #16930
Re: FreeTDS 1.1 Release Candidate 1
Mon, 4 Feb 2019 15:47:56 -0600
Igor Korot <[email protected]> • #16929
FreeTDS 1.1 Release Candidate 1
Mon, 4 Feb 2019 19:41:40 +0000
Frediano Ziglio <[email protected]> • #16928
Re: How to have a better control on how the tds use the openssl?
Wed, 9 Jan 2019 17:44:48 +0000
Rick Qing Xu via FreeTDS <[email protected]> • #16927
Re: UTF-8 issue
Wed, 9 Jan 2019 09:00:05 -0800 (Pacific Standard Time)
Peter Deacon <[email protected]> • #16926
Re: How to have a better control on how the tds use the openssl?
Wed, 9 Jan 2019 15:54:29 +0000
Frediano Ziglio <[email protected]> • #16925
Re: UTF-8 issue
Wed, 9 Jan 2019 13:26:51 +0000
Frediano Ziglio <[email protected]> • #16924
Re: How to have a better control on how the tds use the openssl?
Mon, 7 Jan 2019 19:16:19 +0000
Rick Qing Xu via FreeTDS <[email protected]> • #16923
Re: UTF-8 issue
Wed, 9 Jan 2019 06:52:05 +0000
Deepa Umesh <[email protected]> • #16922
Re: UTF-8 issue
Tue, 8 Jan 2019 09:27:53 -0800 (Pacific Standard Time)
Peter Deacon <[email protected]> • #16921
Re: UTF-8 issue
Mon, 7 Jan 2019 19:53:34 -0600
Igor Korot <[email protected]> • #16920
Re: UTF-8 issue
Tue, 8 Jan 2019 10:40:20 +0000
Deepa Umesh <[email protected]> • #16919
Re: UTF-8 issue
Tue, 8 Jan 2019 00:19:50 -0800 (Pacific Standard Time)
Peter Deacon <[email protected]> • #16918
Re: UTF-8 issue
Tue, 8 Jan 2019 06:41:11 +0000
Deepa Umesh <[email protected]> • #16917
Re: UTF-8 issue
Fri, 4 Jan 2019 09:16:01 +0000
Frediano Ziglio <[email protected]> • #16916
UTF-8 issue
Wed, 2 Jan 2019 06:14:31 +0000
Deepa Umesh <[email protected]> • #16915
Re: How to have a better control on how the tds use the openssl?
Fri, 21 Dec 2018 22:39:17 +0000
Frediano Ziglio <[email protected]> • #16914
Re: How to have a better control on how the tds use the openssl?
Tue, 18 Dec 2018 18:35:02 +0000
Rick Qing Xu via FreeTDS <[email protected]> • #16913
Re: How to have a better control on how the tds use the openssl?
Tue, 18 Dec 2018 18:19:18 +0000
Frediano Ziglio <[email protected]> • #16912
How to have a better control on how the tds use the openssl?
Thu, 13 Dec 2018 19:58:25 +0000
Rick Qing Xu via FreeTDS <[email protected]> • #16911
Re: Asynchronous calls
Fri, 30 Nov 2018 21:43:37 +0000
Frediano Ziglio <[email protected]> • #16910
Re: Pending patches
Tue, 23 Oct 2018 15:18:08 +0000
"Ucko, Aaron \(NIH/NLM/NCBI\) \[E\] via FreeTDS" <[email protected]> • #16909
Re: SQL_SUCCEEDED macro / SQL_NO_DATA for CREATE TABLE
Fri, 19 Oct 2018 16:35:17 +0200
Sebastien FLAESCH <[email protected]> • #16908
Re: SQL_SUCCEEDED macro / SQL_NO_DATA for CREATE TABLE
Fri, 19 Oct 2018 12:08:27 +0100
Frediano Ziglio <[email protected]> • #16907
Re: Debugging
Mon, 15 Oct 2018 12:37:50 -0500
Igor Korot <[email protected]> • #16906
Re: Debugging
Mon, 15 Oct 2018 18:31:52 +0100
Frediano Ziglio <[email protected]> • #16905
Debugging
Sun, 14 Oct 2018 00:15:49 -0500
Igor Korot <[email protected]> • #16904
Asynchronous calls
Wed, 10 Oct 2018 18:29:43 +0200
Sebastien FLAESCH <[email protected]> • #16903
Re: SQLExecDirect() + SQLDataParam() + SQLPutData() fails
Wed, 10 Oct 2018 17:15:15 +0100
Frediano Ziglio <[email protected]> • #16902
Re: SQLExecDirect() + SQLDataParam() + SQLPutData() fails
Wed, 10 Oct 2018 17:14:07 +0100
Frediano Ziglio <[email protected]> • #16901
SQL_SUCCEEDED macro / SQL_NO_DATA for CREATE TABLE
Wed, 10 Oct 2018 16:43:37 +0200
Sebastien FLAESCH <[email protected]> • #16900
Re: SQLExecDirect() + SQLDataParam() + SQLPutData() fails
Wed, 10 Oct 2018 12:17:54 +0200
Sebastien FLAESCH <[email protected]> • #16899
Re: SQLExecDirect() + SQLDataParam() + SQLPutData() fails
Wed, 10 Oct 2018 12:04:35 +0200
Sebastien FLAESCH <[email protected]> • #16898
Re: FreeTDS question about text size
Sat, 6 Oct 2018 18:51:23 +0100
Frediano Ziglio <[email protected]> • #16897
Re: FreeTDS question about text size
Sat, 6 Oct 2018 00:50:25 -0500
Igor Korot <[email protected]> • #16896
Re: SQLDescribeCol
Sat, 6 Oct 2018 00:48:17 -0500
Igor Korot <[email protected]> • #16895
FreeTDS question about text size
Fri, 5 Oct 2018 21:39:41 +0000
"Jacopille, David" <[email protected]> • #16894
Re: SQLDescribeCol
Sat, 6 Oct 2018 18:26:49 +0100
Frediano Ziglio <[email protected]> • #16893
SQLDescribeCol
Sat, 6 Oct 2018 00:21:23 -0500
Igor Korot <[email protected]> • #16892
Re: SQLExecDirect() + SQLDataParam() + SQLPutData() fails
Tue, 11 Sep 2018 22:42:45 +0200
Frediano Ziglio <[email protected]> • #16891
Re: Pending patches
Wed, 22 Aug 2018 15:40:29 +0000
"Ucko, Aaron (NIH/NLM/NCBI) [E]" <[email protected]> • #16890
Re: Windows build/install
Sat, 11 Aug 2018 12:58:33 +0100
Frediano Ziglio <[email protected]> • #16889
Pending patches
Sat, 11 Aug 2018 08:07:51 +0100
Frediano Ziglio <[email protected]> • #16888
Re: Securely specifying passwords for freebcp and such
Sat, 11 Aug 2018 07:58:04 +0100
Frediano Ziglio <[email protected]> • #16887
Re: FreeTDS +SQL Anywhere?
Fri, 10 Aug 2018 06:43:47 +0100
Frediano Ziglio <[email protected]> • #16886
FreeTDS +SQL Anywhere?
Mon, 30 Jul 2018 15:30:28 +0200
Marsupilami79 <[email protected]> • #16885
Securely specifying passwords for freebcp and such
Thu, 2 Aug 2018 19:45:42 +0000
Benjamin Moody <[email protected]> • #16884
Re: freeTDS on Windows
Tue, 31 Jul 2018 07:52:44 -0500
Igor Korot <[email protected]> • #16883
Re: freeTDS on Windows
Tue, 31 Jul 2018 07:43:02 +0100
Frediano Ziglio <[email protected]> • #16882
Re: freeTDS on Windows
Mon, 30 Jul 2018 07:59:21 -0500
Igor Korot <[email protected]> • #16881
Re: freeTDS on Windows
Mon, 30 Jul 2018 07:34:56 +0100
Frediano Ziglio <[email protected]> • #16880
Re: Appveyor master artifacts
Sun, 29 Jul 2018 23:36:20 -0400
Alex <[email protected]> • #16879
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.