gmane.comp.python.db archive

418 archived articles, newest first (page 3 of 5). Latest articles →

ANN: eGenix mxODBC 3.3.6 - Python ODBC Database Interface
Wed, 16 Nov 2016 17:55:49 +0100
"eGenix Team: M.-A. Lemburg" <[email protected]> • #3878
SQLObject 3.1.0
Tue, 16 Aug 2016 21:16:36 +0200
Oleg Broytman <[email protected]> • #3877
Re: PEP 249
Tue, 28 Jun 2016 18:02:06 +0900
INADA Naoki <[email protected]> • #3876
Re: PEP 249
Mon, 27 Jun 2016 13:51:11 +0200
"M.-A. Lemburg" <[email protected]> • #3875
PEP 249
Fri, 24 Jun 2016 16:31:10 +0200
Sigurd Jervelund Hansen <[email protected]> • #3874
How to set connection timezone in DBAPI-presto connection
Tue, 14 Jun 2016 15:18:11 +0530
Praveen Kumar <[email protected]> • #3873
PEP 249
Tue, 14 Jun 2016 01:59:07 +0000
"Ren, Jianxin (Nokia - CN/Hangzhou)" <[email protected]> • #3872
Need help regarding connection establish with db informix
Fri, 3 Jun 2016 13:35:22 +0500
Muhammad Amir Latif <[email protected]> • #3871
SQLObject 3.0.0
Wed, 1 Jun 2016 18:01:53 +0200
Oleg Broytman <[email protected]> • #3870
SQLObject 2.2
Sun, 8 May 2016 09:33:35 +0200
Oleg Broytman <[email protected]> • #3869
Re: numbers with correct decimals places
Thu, 28 Apr 2016 13:52:49 +0200
"M.-A. Lemburg" <[email protected]> • #3868
numbers with correct decimals places
Wed, 27 Apr 2016 10:14:39 -0300
Edilson Santos <[email protected]> • #3867
Re: Need clarifications/help on preserving revisions of files/permissions using Python
Mon, 25 Jan 2016 12:16:46 +0100
"M.-A. Lemburg" <[email protected]> • #3866
Need clarifications/help on preserving revisions of files/permissions using Python
Fri, 22 Jan 2016 14:15:03 +0530
madhusudhan achar <[email protected]> • #3865
Re: Should Binary accept unicode string?
Sat, 16 Jan 2016 22:51:54 -0500
Mike Bayer <[email protected]> • #3864
Re: Should Binary accept unicode string?
Sat, 16 Jan 2016 20:30:56 +0100
"M.-A. Lemburg" <[email protected]> • #3863
Re: Should Binary accept unicode string?
Sat, 16 Jan 2016 10:27:58 -0500
Mike Bayer <[email protected]> • #3862
Re: Should Binary accept unicode string?
Fri, 15 Jan 2016 15:14:59 -0700
"Vernon D. Cole" <[email protected]> • #3861
Re: Should Binary accept unicode string?
Fri, 15 Jan 2016 12:21:33 -0500
Mike Bayer <[email protected]> • #3860
Re: Should Binary accept unicode string?
Fri, 15 Jan 2016 17:15:52 +0100
"M.-A. Lemburg" <[email protected]> • #3859
Re: Should Binary accept unicode string?
Fri, 15 Jan 2016 10:52:19 -0500
Mike Bayer <[email protected]> • #3858
Re: Should Binary accept unicode string?
Fri, 15 Jan 2016 15:47:07 +0100
"M.-A. Lemburg" <[email protected]> • #3857
Re: Should Binary accept unicode string?
Fri, 15 Jan 2016 09:39:24 -0500
Mike Bayer <[email protected]> • #3856
Should Binary accept unicode string?
Tue, 12 Jan 2016 21:59:08 +0900
INADA Naoki <[email protected]> • #3855
Re: PEP 249--connection problems
Mon, 11 Jan 2016 08:32:47 +0900
INADA Naoki <[email protected]> • #3854
PEP 249--connection problems
Sun, 10 Jan 2016 14:25:45 -0500
"greg tobias" <[email protected]> • #3853
Re: SQL CONNECTION
Mon, 4 Jan 2016 14:26:48 +1100
Andy Todd <[email protected]> • #3852
SQL CONNECTION
Wed, 30 Dec 2015 14:31:43 +0000
Dale Wheeler <[email protected]> • #3851
Re: Would like to challenge DBAPI on callproc's return value
Tue, 08 Dec 2015 03:51:41 +0000
Milosz Kosmider <[email protected]> • #3850
Re: Would like to challenge DBAPI on callproc's return value
Mon, 7 Dec 2015 19:35:37 +0100
"M.-A. Lemburg" <[email protected]> • #3849
Re: Would like to challenge DBAPI on callproc's return value
Sun, 06 Dec 2015 19:10:15 +0000
Milosz Kosmider <[email protected]> • #3848
Re: Would like to challenge DBAPI on callproc's return value
Fri, 4 Dec 2015 16:04:46 -0500
Mike Bayer <[email protected]> • #3847
Re: Would like to challenge DBAPI on callproc's return value
Wed, 2 Dec 2015 22:45:51 +0100
"M.-A. Lemburg" <[email protected]> • #3846
Would like to challenge DBAPI on callproc's return value
Tue, 1 Dec 2015 00:40:12 -0500
Milosz Kosmider <[email protected]> • #3845
ANN: eGenix mxODBC Connect 2.1.5 - Remote Python Database Interface
Fri, 23 Oct 2015 11:30:11 +0200
"eGenix Team: M.-A. Lemburg" <[email protected]> • #3844
ANN: eGenix mxODBC Connect 2.1.4 - Remote Python Database Interface
Wed, 23 Sep 2015 10:12:18 +0200
"eGenix Team: M.-A. Lemburg" <[email protected]> • #3843
ANN: eGenix mxODBC 3.3.5 - Python ODBC Database Interface
Wed, 19 Aug 2015 12:06:38 +0200
"eGenix Team: M.-A. Lemburg" <[email protected]> • #3842
ANN: eGenix mxODBC 3.3.4 - Python ODBC Database Interface
Wed, 12 Aug 2015 12:03:41 +0200
"eGenix Team: M.-A. Lemburg" <[email protected]> • #3841
ANN: eGenix mxODBC 3.3.3 - Python ODBC Database Interface
Thu, 25 Jun 2015 10:12:51 +0200
"eGenix Team: M.-A. Lemburg" <[email protected]> • #3840
ANN: eGenix mxODBC Connect 2.1.3 - Remote Python Database Interface
Wed, 13 May 2015 10:58:14 +0200
"eGenix Team: M.-A. Lemburg" <[email protected]> • #3839
SQLObject 3.0.0a1
Fri, 27 Mar 2015 21:26:40 +0100
Oleg Broytman <[email protected]> • #3838
SQLObject 2.1.2 and 1.7.5
Sun, 15 Mar 2015 05:18:13 +0100
Oleg Broytman <[email protected]> • #3837
ANN: eGenix mxODBC 3.3.2 - Python ODBC Database Interface
Thu, 12 Mar 2015 11:57:07 +0100
"eGenix Team: M.-A. Lemburg" <[email protected]> • #3836
SQLObject 2.1.1 and 1.7.4
Mon, 9 Mar 2015 23:54:25 +0100
Oleg Broytman <[email protected]> • #3835
Re: "lists of tuples" vs. "tuples of tuples"
Tue, 10 Feb 2015 18:08:48 -0500
Michael Bayer <[email protected]> • #3834
Re: "lists of tuples" vs. "tuples of tuples"
Tue, 10 Feb 2015 16:28:44 -0500
Peter Eisentraut <[email protected]> • #3833
Re: "lists of tuples" vs. "tuples of tuples"
Tue, 3 Feb 2015 18:10:34 -0500
Michael Bayer <[email protected]> • #3832
Re: "lists of tuples" vs. "tuples of tuples"
Tue, 03 Feb 2015 22:12:17 +0100
"M.-A. Lemburg" <[email protected]> • #3831
Re: "lists of tuples" vs. "tuples of tuples"
Tue, 3 Feb 2015 15:30:18 -0500
Michael Bayer <[email protected]> • #3830
Re: "lists of tuples" vs. "tuples of tuples"
Tue, 3 Feb 2015 11:26:00 -0700
"Vernon D. Cole" <[email protected]> • #3829
Re: "lists of tuples" vs. "tuples of tuples"
Mon, 2 Feb 2015 08:41:16 -0500
Michael Bayer <[email protected]> • #3828
Re: "lists of tuples" vs. "tuples of tuples"
Mon, 02 Feb 2015 12:13:54 +0100
"M.-A. Lemburg" <[email protected]> • #3827
"lists of tuples" vs. "tuples of tuples"
Sun, 1 Feb 2015 16:47:58 -0500
Michael Bayer <[email protected]> • #3826
SQLObject 2.1.0
Tue, 6 Jan 2015 16:54:12 +0100
Oleg Broytman <[email protected]> • #3825
Help with finding tutors for Python, Linux, R, Perl, Octave, MATLAB and/or Cytoscape for yeast microarray analysis, next generation sequencing and constructing gene interaction networks
Sat, 3 Jan 2015 21:48:56 -0600
thomas hahn <[email protected]> • #3824
Re: DBAPI 3.0: Unified parameter style
Sun, 28 Dec 2014 08:55:22 -0700
"Vernon D. Cole" <[email protected]> • #3823
Re: API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Fri, 17 May 2013 20:07:28 +0200
"Dieter Maurer" <[email protected]> • #3822
Re: DBAPI 3.0: Unified parameter style
Mon, 16 Sep 2013 12:15:51 +0200
"Dieter Maurer" <[email protected]> • #3821
Re: Improved support for prepared SQL statements
Sun, 21 Dec 2014 19:05:55 +0000
Tony Locke <[email protected]> • #3820
Re: Improved support for prepared SQL statements
Mon, 22 Dec 2014 00:59:13 -0500
Michael Bayer <[email protected]> • #3819
Re: Improved support for prepared SQL statements
Sun, 21 Dec 2014 21:17:23 +0100
"M.-A. Lemburg" <[email protected]> • #3818
Re: Improved support for prepared SQL statements
Sun, 21 Dec 2014 20:59:33 +0100
"M.-A. Lemburg" <[email protected]> • #3817
Re: Improved support for prepared SQL statements
Sun, 21 Dec 2014 14:56:24 -0500
Michael Bayer <[email protected]> • #3816
Re: Improved support for prepared SQL statements
Sun, 21 Dec 2014 14:46:19 -0500
Michael Bayer <[email protected]> • #3815
Re: Improved support for prepared SQL statements
Sun, 21 Dec 2014 20:43:09 +0100
"M.-A. Lemburg" <[email protected]> • #3814
Re: Improved support for prepared SQL statements
Sun, 21 Dec 2014 20:10:39 +0100
"M.-A. Lemburg" <[email protected]> • #3813
Re: Improved support for prepared SQL statements
Sun, 21 Dec 2014 13:40:08 -0500
Michael Bayer <[email protected]> • #3812
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 22:33:19 +0900
INADA Naoki <[email protected]> • #3811
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 20:00:38 +0100
SF Markus Elfring <[email protected]> • #3810
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 20:27:05 +0900
INADA Naoki <[email protected]> • #3809
Re: Improved support for prepared SQL statements
Fri, 19 Dec 2014 00:48:24 +0900
INADA Naoki <[email protected]> • #3808
SQLObject 2.0
Sat, 20 Dec 2014 19:20:19 +0100
Oleg Broytman <[email protected]> • #3807
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 18:12:36 -0500
Michael Bayer <[email protected]> • #3806
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 23:55:50 +0100
"M.-A. Lemburg" <[email protected]> • #3805
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 17:19:56 -0500
Michael Bayer <[email protected]> • #3804
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 16:42:47 -0500
Michael Bayer <[email protected]> • #3803
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 22:36:41 +0100
"M.-A. Lemburg" <[email protected]> • #3802
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 15:57:01 -0500
Michael Bayer <[email protected]> • #3801
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 21:56:27 +0100
"M.-A. Lemburg" <[email protected]> • #3800
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 21:39:45 +0100
"M.-A. Lemburg" <[email protected]> • #3799
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 15:23:02 -0500
Michael Bayer <[email protected]> • #3798
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 12:37:10 -0700
"Vernon D. Cole" <[email protected]> • #3797
SQLObject 1.7.3
Thu, 18 Dec 2014 18:23:17 +0100
Oleg Broytman <[email protected]> • #3796
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 10:59:39 -0500
Michael Bayer <[email protected]> • #3795
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 10:46:35 -0500
Michael Bayer <[email protected]> • #3794
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 10:39:00 -0500
Michael Bayer <[email protected]> • #3793
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 13:33:02 +0100
"M.-A. Lemburg" <[email protected]> • #3792
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 11:39:24 +0100
"M.-A. Lemburg" <[email protected]> • #3791
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 08:10:09 +0100
SF Markus Elfring <[email protected]> • #3790
Re: Improved support for prepared SQL statements
Wed, 17 Dec 2014 19:37:57 +0000
Tony Locke <[email protected]> • #3789
Re: Improved support for prepared SQL statements
Wed, 17 Dec 2014 16:18:26 +0100
SF Markus Elfring <[email protected]> • #3788
Re: Improved support for prepared SQL statements
Thu, 18 Dec 2014 03:13:44 +0900
INADA Naoki <[email protected]> • #3787
Re: Improved support for prepared SQL statements
Wed, 17 Dec 2014 15:38:37 +0100
SF Markus Elfring <[email protected]> • #3786
Re: Improved support for prepared SQL statements
Wed, 17 Dec 2014 14:50:47 +0100
SF Markus Elfring <[email protected]> • #3785
Re: Improved support for prepared SQL statements
Wed, 17 Dec 2014 22:25:20 +0100
"M.-A. Lemburg" <[email protected]> • #3784
Re: Improved support for prepared SQL statements
Wed, 17 Dec 2014 22:02:42 +0100
"M.-A. Lemburg" <[email protected]> • #3783
Re: Improved support for prepared SQL statements
Wed, 17 Dec 2014 12:54:01 -0500
Michael Bayer <[email protected]> • #3782
Re: Improved support for prepared SQL statements
Wed, 17 Dec 2014 16:41:12 +0100
"M.-A. Lemburg" <[email protected]> • #3781
Re: Improved support for prepared SQL statements
Wed, 17 Dec 2014 16:03:09 +0100
"M.-A. Lemburg" <[email protected]> • #3780
Re: Improved support for prepared SQL statements
Wed, 17 Dec 2014 15:21:43 +0100
"M.-A. Lemburg" <[email protected]> • #3779
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.