gmane.comp.python.db.psycopg.devel archive
1213 archived articles, newest first (page 9 of 13). Latest articles →
Re: connection pooling
Thu, 19 Mar 2009 20:32:09 +0100connection pooling
Thu, 19 Mar 2009 12:31:04 -0600Re: Psycopg 2.0.9 on Windows
Wed, 11 Mar 2009 15:07:51 -0600 (MDT)Re: Psycopg 2.0.9 on Windows
Wed, 11 Mar 2009 16:12:31 -0500Psycopg 2.0.9 on Windows
Wed, 11 Mar 2009 13:13:01 -0500Re: Access to bzr repository
Tue, 10 Mar 2009 12:37:38 +1000Re: Access to bzr repository
Mon, 9 Mar 2009 22:55:22 -0500Re: Access to bzr repository
Tue, 10 Mar 2009 11:26:05 +0900Access to bzr repository
Mon, 9 Mar 2009 16:46:53 -0500Re: ProgrammingError: can't adapt (None)
Mon, 09 Mar 2009 22:05:20 +0100Re: ProgrammingError: can't adapt (None)
Mon, 09 Mar 2009 21:33:07 +0100Re: ProgrammingError: can't adapt (None)
Mon, 09 Mar 2009 19:42:22 +0100Re: Segfault in in PyString_FromStringAndSize
Mon, 9 Mar 2009 15:16:50 -0200Re: Segfault in in PyString_FromStringAndSize
Mon, 09 Mar 2009 15:23:30 +0100Re: ProgrammingError: can't adapt (None)
Mon, 09 Mar 2009 09:27:25 +0100Re: Segfault in in PyString_FromStringAndSize
Sat, 7 Mar 2009 12:54:22 -0200Re: Wierd "ProgrammingError" with "E" string prefix
Fri, 06 Mar 2009 18:36:02 +0100ProgrammingError: can't adapt (None)
Fri, 06 Mar 2009 18:32:17 +0100Re: Segfault in in PyString_FromStringAndSize
Fri, 6 Mar 2009 13:12:12 -0200Re: Segfault in in PyString_FromStringAndSize
Fri, 6 Mar 2009 10:06:04 -0500Re: Segfault in in PyString_FromStringAndSize
Fri, 6 Mar 2009 12:27:16 -0200Segfault in in PyString_FromStringAndSize
Thu, 5 Mar 2009 12:09:38 -0200Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 23:33:16 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 23:07:23 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 16:37:20 -0500Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 21:52:48 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 21:51:59 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 21:25:32 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 20:46:10 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 11:04:27 -0800Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 19:52:18 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 19:20:37 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 19:19:08 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 09:56:11 -0800Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 09:52:51 -0800Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 15:55:52 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 15:51:23 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 06:30:04 -0800Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 15:33:49 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 15:25:57 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 12:04:46 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 12:33:19 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 11:54:39 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 11:18:08 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 04 Mar 2009 09:59:34 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Wed, 4 Mar 2009 09:41:39 +0100Re: Wierd "ProgrammingError" with "E" string prefix
Tue, 03 Mar 2009 14:58:35 -0800Wierd "ProgrammingError" with "E" string prefix
Tue, 03 Mar 2009 23:36:51 +0100Re: does the executemany() limitation with result sets apply to INSERT..RETURNING ?
Tue, 03 Mar 2009 16:57:15 +0100Re: does the executemany() limitation with result sets apply to INSERT..RETURNING ?
Tue, 3 Mar 2009 08:59:03 -0500Re: does the executemany() limitation with result sets apply to INSERT..RETURNING ?
Mon, 2 Mar 2009 20:29:11 -0500Re: does the executemany() limitation with result sets apply to INSERT..RETURNING ?
Mon, 02 Mar 2009 23:47:33 +0100Re: does the executemany() limitation with result sets apply to INSERT..RETURNING ?
Mon, 2 Mar 2009 17:32:09 -0500Re: problem with timezone parsing
Mon, 2 Mar 2009 11:39:01 +0100Re: problem with timezone parsing
Mon, 02 Mar 2009 11:34:05 +0100Re: problem with timezone parsing
Mon, 2 Mar 2009 11:30:14 +0100Re: problem with timezone parsing
Mon, 02 Mar 2009 09:31:06 +0100Re: does the executemany() limitation with result sets apply to INSERT..RETURNING ?
Mon, 02 Mar 2009 09:09:19 +0100does the executemany() limitation with result sets apply to INSERT..RETURNING ?
Sun, 1 Mar 2009 15:07:16 -0500Re: problem with timezone parsing
Wed, 25 Feb 2009 14:07:40 +0100Re: problem with timezone parsing
Wed, 25 Feb 2009 14:04:43 +0100Re: problem with timezone parsing
Wed, 25 Feb 2009 14:00:03 +0100Re: problem with timezone parsing
Wed, 25 Feb 2009 13:52:50 +0100Re: problem with timezone parsing
Wed, 25 Feb 2009 13:44:17 +0100Re: Array with a lower bound>1, PostgreSQL 8.3.6
Wed, 25 Feb 2009 13:08:37 +0100Re: problem with timezone parsing
Wed, 25 Feb 2009 13:04:48 +0100Re: Array with a lower bound>1, PostgreSQL 8.3.6
Wed, 25 Feb 2009 12:58:26 +0100Re: Array with a lower bound>1, PostgreSQL 8.3.6
Wed, 25 Feb 2009 12:53:08 +0100Re: Array with a lower bound>1, PostgreSQL 8.3.6
Wed, 25 Feb 2009 10:06:13 +0100Re: Array with a lower bound>1, PostgreSQL 8.3.6
Tue, 24 Feb 2009 13:03:46 -0800Re: Array with a lower bound>1, PostgreSQL 8.3.6
Tue, 24 Feb 2009 21:42:42 +0100Re: Array with a lower bound>1, PostgreSQL 8.3.6
Tue, 24 Feb 2009 21:35:50 +0100Re: Array with a lower bound>1, PostgreSQL 8.3.6
Tue, 24 Feb 2009 17:25:38 -0300Re: psycopg2
Tue, 24 Feb 2009 21:22:06 +0100Re: Array with a lower bound>1, PostgreSQL 8.3.6
Tue, 24 Feb 2009 21:15:40 +0100Re: problem with timezone parsing
Tue, 24 Feb 2009 14:46:19 -0500Re: Array with a lower bound>1, PostgreSQL 8.3.6
Tue, 24 Feb 2009 10:20:48 -0800Re: Array with a lower bound>1, PostgreSQL 8.3.6
Tue, 24 Feb 2009 17:07:46 +0100Re: Array with a lower bound>1, PostgreSQL 8.3.6
Tue, 24 Feb 2009 16:36:21 +0100Array with a lower bound>1, PostgreSQL 8.3.6
Tue, 24 Feb 2009 14:22:34 +0100Re: problem with timezone parsing
Tue, 24 Feb 2009 11:01:51 +0100Re: problem with timezone parsing
Tue, 24 Feb 2009 10:49:13 +0100Re: problem with timezone parsing
Tue, 24 Feb 2009 10:46:17 +0100Re: problem with timezone parsing
Tue, 24 Feb 2009 10:27:12 +0100RELEASE: Psycopg 2.0.9
Mon, 23 Feb 2009 21:49:55 +0100Re: problem with timezone parsing
Mon, 23 Feb 2009 18:11:20 +0100Re: problem with timezone parsing
Tue, 24 Feb 2009 01:40:43 +1100Re: problem with timezone parsing
Sun, 22 Feb 2009 23:27:56 +0100Re: problem with timezone parsing
Wed, 18 Feb 2009 23:18:51 +0100Re: problem with timezone parsing
Wed, 18 Feb 2009 21:29:47 +0100Re: problem with timezone parsing
Wed, 18 Feb 2009 20:13:52 +0100Re: problem with timezone parsing
Wed, 18 Feb 2009 20:11:18 +0100Re: problem with timezone parsing
Wed, 18 Feb 2009 16:56:37 +0100Re: problem with timezone parsing
Wed, 18 Feb 2009 23:28:34 +0900Re: problem with timezone parsing
Wed, 18 Feb 2009 14:04:39 +0100Re: problem with timezone parsing
Wed, 18 Feb 2009 08:36:25 +0900Re: problem with timezone parsing
Tue, 17 Feb 2009 18:00:09 +0100Re: problem with timezone parsing
Tue, 17 Feb 2009 17:51:19 +0100Re: problem with timezone parsing
Tue, 17 Feb 2009 17:00:53 +0100Re: problem with timezone parsing
Tue, 17 Feb 2009 16:57:35 +0100
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.