Mailing lists [psycopg]

1 January 2017

• 14:11   [psycopg] Solving the SQL composition problem Daniele Varrazzo

2 January 2017

• 00:40   Re: [psycopg] Solving the SQL composition problem Adrian Klaver
• 01:03   Re: [psycopg] Solving the SQL composition problem Karsten Hilbert
• 01:12   Re: [psycopg] speed concerns with executemany() mike bayer
• 01:14   Re: [psycopg] speed concerns with executemany() mike bayer
• 02:33   Re: [psycopg] speed concerns with executemany() Adrian Klaver
• 04:09   Re: [psycopg] Solving the SQL composition problem Adrian Klaver
• 16:04   Re: [psycopg] Solving the SQL composition problem Oleksandr Shulgin
• 19:03   Re: [psycopg] speed concerns with executemany() Daniele Varrazzo
• 19:05   Re: [psycopg] speed concerns with executemany() Daniele Varrazzo
• 21:05   Re: [psycopg] Solving the SQL composition problem Jim Nasby
• 21:16   Re: [psycopg] Solving the SQL composition problem Adrian Klaver
• 21:21   Re: [psycopg] speed concerns with executemany() Adrian Klaver
• 21:35   Re: [psycopg] speed concerns with executemany() Adrian Klaver
• 21:46   Re: [psycopg] speed concerns with executemany() Karsten Hilbert
• 22:07   Re: [psycopg] speed concerns with executemany() Daniele Varrazzo
• 22:10   Re: [psycopg] speed concerns with executemany() Daniele Varrazzo
• 22:15   Re: [psycopg] speed concerns with executemany() Adrian Klaver
• 22:16   Re: [psycopg] speed concerns with executemany() Karsten Hilbert
• 22:21   Re: [psycopg] Solving the SQL composition problem Daniele Varrazzo
• 22:24   Re: [psycopg] speed concerns with executemany() Daniele Varrazzo
• 22:27   Re: [psycopg] speed concerns with executemany() Karsten Hilbert
• 22:32   Re: [psycopg] speed concerns with executemany() Karsten Hilbert
• 22:35   Re: [psycopg] speed concerns with executemany() Adrian Klaver
• 23:03   Re: [psycopg] Solving the SQL composition problem Adrian Klaver

3 January 2017

• 01:33   Re: [psycopg] speed concerns with executemany() Oswaldo
• 01:36   Re: [psycopg] speed concerns with executemany() Oswaldo
• 22:24   Re: [psycopg] Solving the SQL composition problem Jim Nasby
• 22:33   Re: [psycopg] Solving the SQL composition problem Daniele Varrazzo
• 22:35   Re: [psycopg] Solving the SQL composition problem Adrian Klaver
• 22:35   Re: [psycopg] Solving the SQL composition problem Christophe Pettus
• 22:40   Re: [psycopg] Solving the SQL composition problem Daniele Varrazzo

4 January 2017

• 06:03   Re: [psycopg] Solving the SQL composition problem Jim Nasby
• 20:37   [psycopg] Releasing Linux binary packages of psycopg Daniele Varrazzo
• 21:54   Re: [psycopg] Releasing Linux binary packages of psycopg Adrian Klaver

5 January 2017

• 05:50   [psycopg] psycopg2.pool connection recovery/healing Paul Bryan
• 18:49   Re: [psycopg] psycopg2.pool connection recovery/healing Daniele Varrazzo
• 22:51   Re: [psycopg] psycopg2.pool connection recovery/healing Paul Bryan
• 23:32   Re: [psycopg] speed concerns with executemany() Federico Di Gregorio

6 January 2017

• 00:59   Re: [psycopg] Solving the SQL composition problem Adrian Klaver
• 01:00   Re: [psycopg] speed concerns with executemany() Daniele Varrazzo
• 01:26   Re: [psycopg] Solving the SQL composition problem Daniele Varrazzo
• 03:22   Re: [psycopg] Solving the SQL composition problem Adrian Klaver
• 03:23   Re: [psycopg] speed concerns with executemany() Adrian Klaver
• 04:12   Re: [psycopg] speed concerns with executemany() Federico Di Gregorio
• 18:51   Re: [psycopg] Releasing Linux binary packages of psycopg Daniele Varrazzo

9 January 2017

• 22:04   Re: [psycopg] speed concerns with executemany() mike bayer
• 22:45   Re: [psycopg] speed concerns with executemany() Jim Nasby

10 January 2017

• 05:12   Re: [psycopg] speed concerns with executemany() mike bayer

16 January 2017

• 02:32   [psycopg] Turbo ODBC Jim Nasby
• 03:04   Re: [psycopg] Turbo ODBC Adrian Klaver
• 03:19   Re: [psycopg] Turbo ODBC Jim Nasby
• 03:25   Re: [psycopg] Turbo ODBC Adrian Klaver

17 January 2017

• 05:14   Re: [psycopg] Turbo ODBC Jim Nasby
• 05:24   Re: [psycopg] Turbo ODBC Matthew Rocklin
• 05:26   [psycopg] Nested transactions support for code composability Daniel Fortunov
• 05:29   Re: [psycopg] Nested transactions support for code composability Christophe Pettus
• 07:20   Re: [psycopg] Turbo ODBC Wes McKinney
• 07:32   Re: [psycopg] Turbo ODBC Adrian Klaver
• 08:07   Re: [psycopg] Turbo ODBC Jim Nasby
• 11:25   Re: [psycopg] Turbo ODBC Adrian Klaver
• 16:51   Re: [psycopg] Turbo ODBC Uwe L. Korn
• 21:06   Re: [psycopg] Turbo ODBC Jim Nasby
• 21:16   Re: [psycopg] Turbo ODBC Koenig, Michael
• 21:18   Re: [psycopg] Turbo ODBC Uwe L. Korn
• 22:31   Re: [psycopg] Turbo ODBC Jim Nasby

18 January 2017

• 00:34   Re: [psycopg] Turbo ODBC Daniele Varrazzo
• 03:30   Re: [psycopg] Turbo ODBC Jim Nasby

19 January 2017

• 18:23   Re: [psycopg] speed concerns with executemany() Aryeh Leib Taurog

22 January 2017

• 22:49   Re: [psycopg] Nested transactions support for code composability Daniel Fortunov
• 23:22   Re: [psycopg] Nested transactions support for code composability Christophe Pettus
• 23:57   Re: [psycopg] Nested transactions support for code composability Adrian Klaver

23 January 2017

• 00:08   Re: [psycopg] Nested transactions support for code composability Christophe Pettus
• 22:45   Re: [psycopg] Nested transactions support for code composability Jonathan Rogers

29 January 2017

• 23:44   Re: [psycopg] speed concerns with executemany() Aryeh Leib Taurog

30 January 2017

• 17:18   Re: [psycopg] speed concerns with executemany() Daniele Varrazzo

31 January 2017

• 03:51   Re: [psycopg] speed concerns with executemany() Aryeh Leib Taurog
• 04:14   Re: [psycopg] speed concerns with executemany() Aryeh Leib Taurog