FAQ
nameDaniele-Varrazzo
seenFeb 12, 2016
sinceOct 3, 2006
468
posts
14
groups
2
badges

14 groups [ show more ]

psycopg@postgresql.org (269 posts) pgsql-general@postgresql.org (40 posts) db-sig@python.org (38 posts)
db-sig (38)
in python
pgsql-hackers@postgresql.org (30 posts) pgsql-announce@postgresql.org (19 posts)
pgsql-bugs@postgresql.org (14 posts) pgsql-docs@postgresql.org (13 posts) python-list@python.org (13 posts) ansible-project@googlegroups.com (8 posts) pgsql-performance@postgresql.org (7 posts)
python-porting@python.org (7 posts) distutils-sig@python.org (5 posts) zeromq-dev@lists.zeromq.org (3 posts) pgsql-jdbc@postgresql.org (2 posts)

468 posts

Archive for ansible-project@googlegroups.com Feb 2016 Re: [ansible-project] Play single roles in a playbook
Archive for ansible-project@googlegroups.com Feb 2016 [ansible-project] Play single roles in a playbook
Archive for db-sig@python.org Dec 2014 [DB-SIG] Improved support for prepared SQL statements
Archive for ansible-project@googlegroups.com Aug 2014 Re: [ansible-project] Proposal: include_defaults
Archive for ansible-project@googlegroups.com Aug 2014 [ansible-project] Proposal: include_defaults
Archive for ansible-project@googlegroups.com Aug 2014 Re: [ansible-project] Sharing variables defaults across roles
Archive for ansible-project@googlegroups.com Aug 2014 Re: [ansible-project] Sharing variables defaults across roles
Archive for ansible-project@googlegroups.com Aug 2014 Re: [ansible-project] Sharing variables defaults across roles
Archive for ansible-project@googlegroups.com Aug 2014 [ansible-project] Sharing variables defaults across roles
Archive for pgsql-general@postgresql.org Aug 2013 Re: Handling of tz-aware literals in non-tz-aware fields
Archive for pgsql-general@postgresql.org Aug 2013 Handling of tz-aware literals in non-tz-aware fields
Archive for pgsql-performance@postgresql.org May 2013 Re: Best practice when reindexing in production
Archive for pgsql-performance@postgresql.org May 2013 Re: Best practice when reindexing in production
Archive for db-sig@python.org May 2013 [DB-SIG] bind parameters and empty parameter lists
Archive for db-sig@python.org May 2013 [DB-SIG] paramstyle specification (was: Two sample implementations of ['named', 'qmark'] auto switch (a report))
Archive for db-sig@python.org May 2013 [DB-SIG] Two sample implementations of ['named', 'qmark'] auto switch (a report)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] Test suite update for format conversion accuracy.
Archive for db-sig@python.org May 2013 [DB-SIG] Test suite update for format conversion accuracy.
Archive for db-sig@python.org May 2013 [DB-SIG] Test suite update for format conversion accuracy.
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for db-sig@python.org May 2013 [DB-SIG] API 3.0 limiting paramstyle to ['named', 'qmark'] is okay. ('format' is not desirable)
Archive for pgsql-hackers@postgresql.org Apr 2013 Changing schema on the fly
Archive for pgsql-general@postgresql.org Apr 2013 Re: Selecting timestamp from Database
Archive for pgsql-hackers@postgresql.org Mar 2013 Re: A few string fixed
Archive for pgsql-hackers@postgresql.org Mar 2013 A few string fixed
Archive for pgsql-hackers@postgresql.org Feb 2013 Re: [RFC] ideas for a new Python DBAPI driver (was Re: libpq test suite)
Archive for pgsql-general@postgresql.org Feb 2013 Re: libpq compatibility
Archive for psycopg@postgresql.org Jan 2013 Re: pyscopg2 recursive query results differ from psql
Archive for pgsql-hackers@postgresql.org Jan 2013 Re: PL/Python result object str handler
Archive for psycopg@postgresql.org Jan 2013 Re: ZPsycoPGDA: How to contribute
Archive for psycopg@postgresql.org Jan 2013 Re: Repository
Archive for psycopg@postgresql.org Jan 2013 Re: ZPsycoPGDA: How to contribute
Archive for pgsql-bugs@postgresql.org Jan 2013 Re: BUG #7797: datetime + '1 month'::interval is going outside of a month's bounds
Archive for pgsql-bugs@postgresql.org Jan 2013 Re: BUG #7797: datetime + '1 month'::interval is going outside of a month's bounds
Archive for psycopg@postgresql.org Dec 2012 Re: New 9.2 features into the devel branch?
Archive for pgsql-announce@postgresql.org Dec 2012 psycopg 2.4.6 released
Archive for psycopg@postgresql.org Dec 2012 psycopg 2.4.6 released
Archive for pgsql-hackers@postgresql.org Dec 2012 Re: allowing multiple PQclear() calls