pygresql  

Messages by Thread

• [PyGreSQL] PyGreSQL #80: Support PQresultMemorySize() in PostgreSQL 12 PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #80: Support PQresultMemorySize() in PostgreSQL 12 PyGreSQL issue tracker
• [PyGreSQL] [1009] branches/5.0.x/docs: Copy changes from the 5.0.7 tag to the 5.0.x branch. NULL
  • Re: [PyGreSQL] Release checklist Christoph Zwerschke
  • Re: [PyGreSQL] Release checklist D'Arcy Cain
  • Re: [PyGreSQL] Release checklist Christoph Zwerschke
  • Re: [PyGreSQL] Release checklist D'Arcy Cain
  • Re: [PyGreSQL] Release checklist Christoph Zwerschke
  • Re: [PyGreSQL] Release checklist D'Arcy Cain
  • Re: [PyGreSQL] Release checklist Christoph Zwerschke
• [PyGreSQL] [1008] trunk/docs/contents/changelog.rst: Fix minor text issues. NULL
• [PyGreSQL] [1007] Typo. Number is 15, not 13. NULL
• [PyGreSQL] [1006] Number of files in distribution has changed. NULL
• [PyGreSQL] [1005] Sphinx-build is now a symlink to the current version. NULL
• [PyGreSQL] [1003] tags/5.0.7/: Tagging the 5.0.7 release of PyGreSQL NULL
• [PyGreSQL] [1004] tags/5.1/: Tagging the 5.1 release of PyGreSQL NULL
• [PyGreSQL] PyGreSQL 5.1 ready for release Christoph Zwerschke
  • Re: [PyGreSQL] PyGreSQL 5.1 ready for release Justin Pryzby
  • Re: [PyGreSQL] PyGreSQL 5.1 ready for release Christoph Zwerschke
• [PyGreSQL] [1001] trunk/internal.c: Use C89 only (PEP 7) NULL
• [PyGreSQL] [1000] trunk/query.c: Use proper type for len NULL
• [PyGreSQL] [999] trunk/MANIFEST.in: Put additional C files into the manifest template NULL
• [PyGreSQL] [998] trunk/tests/test_classic_connection.py: Fix test for database with cyrillic charset NULL
• [PyGreSQL] [991] trunk: Add some more attributes to the connection object NULL
• [PyGreSQL] [997] trunk/tests: Some more IDE hints NULL
• [PyGreSQL] [996] trunk: Better error messages in inserttable() method NULL
• Re: [PyGreSQL] PyGreSQL #24: Make PyGreSQL thread-safe on the connection level PyGreSQL issue tracker
• [PyGreSQL] [995] trunk: Support autocommit attribute on pgdb connections NULL
• [PyGreSQL] [994] trunk/docs/contents/changelog.rst: Fix typo and whitespace NULL
• [PyGreSQL] [993] trunk/docs/contents/changelog.rst: Don't forget to mention contributors in changelog NULL
• [PyGreSQL] PyGreSQL #79: Use PQconnectdbParams instead of PQsetdbLogin PyGreSQL issue tracker
• [PyGreSQL] [992] Document how to send more parameters with connect NULL
• [PyGreSQL] [990] trunk/setup.py: PostgreSQL 11 support was missing in setup.py NULL
• [PyGreSQL] [989] trunk: Minor whitespace fixes and IDE hints NULL
• [PyGreSQL] [988] trunk/pg.py: Merge additional copyright info into top header NULL
• [PyGreSQL] PyGreSQL #78: Make the c files compile separately PyGreSQL issue tracker
• [PyGreSQL] [987] trunk: Let all source files have the same short header NULL
• [PyGreSQL] [983] trunk/pgmodule.c: Consistent naming of functions in the C module NULL
• [PyGreSQL] [985] trunk: Let single() and variants raise more specific error NULL
• [PyGreSQL] [984] trunk/tests/test_classic_connection.py: Test existence of all query methods NULL
• [PyGreSQL] [980] trunk: Query methods for getting single rows and columns NULL
  • Re: [PyGreSQL] [980] trunk: Query methods for getting single rows and columns Justin Pryzby
  • Re: [PyGreSQL] [980] trunk: Query methods for getting single rows and columns Christoph Zwerschke
  • Re: [PyGreSQL] [980] trunk: Query methods for getting single rows and columns Christoph Zwerschke
  • Re: [PyGreSQL] [980] trunk: Query methods for getting single rows and columns Justin Pryzby
  • Re: [PyGreSQL] [980] trunk: Query methods for getting single rows and columns Christoph Zwerschke
• [PyGreSQL] [978] trunk: Make classic query work as iterator NULL
• [PyGreSQL] [979] Add version note for get_as_list/dict NULL
• [PyGreSQL] [977] trunk: Use the term "registered type" (not "regular" type) NULL
• [PyGreSQL] [976] trunk/: Ignore .bak, .log and .coverage files NULL
• [PyGreSQL] [975] trunk/docs/contents/pg/query.rst: Add a note about dictresult() with duplicate fields NULL
• [PyGreSQL] [974] trunk/pg.py: Better name for frequent simple types mapping. NULL
• [PyGreSQL] [973] trunk/docs/contents/pg: Add note about executing multiple SQL commands NULL
• [PyGreSQL] [972] trunk/pg.py: Speed-up guessing simple types NULL
• [PyGreSQL] [971] Minor code simplification in format_query() NULL
• [PyGreSQL] [970] trunk/pg.py: Avoid raising AttributeError NULL
• [PyGreSQL] [969] trunk: Shebang should not be followed by a blank NULL
• [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted() PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted() PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted() PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted() PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted() Justin Pryzby
  • Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted() Christoph Zwerschke
  • Re: [PyGreSQL] PyGreSQL #77: Bad performance of query_formatted() PyGreSQL issue tracker
• [PyGreSQL] query logging of prepared statements Justin Pryzby
• [PyGreSQL] should dictresult warn if column name is reused ? Justin Pryzby
  • Re: [PyGreSQL] should dictresult warn if column name is reused ? D'Arcy Cain
  • Re: [PyGreSQL] should dictresult warn if column name is reused ? Justin Pryzby
  • Re: [PyGreSQL] should dictresult warn if column name is reused ? Christoph Zwerschke
  • Re: [PyGreSQL] should dictresult warn if column name is reused ? D'Arcy Cain
• [PyGreSQL] use_regtypes Justin Pryzby
  • Re: [PyGreSQL] use_regtypes Christoph Zwerschke
• Re: [PyGreSQL] PyGreSQL #16: Make use of PQexecParams() and PQprepare() PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #16: Make use of PQexecParams() and PQprepare() PyGreSQL issue tracker
• [PyGreSQL] [968] trunk/docs/contents: Remove comments meant for review from docs NULL
• [PyGreSQL] [967] trunk/docs/contents/pg: Some more improvements to the docs by Justin Pryzby NULL
• [PyGreSQL] [966] trunk/docs/contents/changelog.rst: Update changelog NULL
• [PyGreSQL] [965] trunk/tests/test_dbapi20_copy.py: Avoid warning in Python 3.7 (and error later in 3.8) NULL
• [PyGreSQL] [964] trunk: Graceful exit of DB destructor on closed connection NULL
• [PyGreSQL] [963] trunk/docs/contents/pg/module.rst: Fix doc error: get/set_cast_hook are connection methods NULL
• [PyGreSQL] [962] trunk/docs/contents: Some improvements to the docs by Justin Pryzby NULL
• [PyGreSQL] query formatting is nearly 10x slower than query Justin Pryzby
  • Re: [PyGreSQL] query formatting is nearly 10x slower than query Justin Pryzby
  • Re: [PyGreSQL] query formatting is nearly 10x slower than query Christoph Zwerschke
• [PyGreSQL] [960] trunk: Update version numbers NULL
• [PyGreSQL] proofread docs Justin Pryzby
  • Re: [PyGreSQL] proofread docs Christoph Zwerschke
  • Re: [PyGreSQL] proofread docs Justin Pryzby
  • Re: [PyGreSQL] proofread docs Christoph Zwerschke
  • Re: [PyGreSQL] proofread docs Justin Pryzby
  • Re: [PyGreSQL] proofread docs Christoph Zwerschke
• [PyGreSQL] [961] trunk: Revert to name of prepared query as positional arg NULL
• [PyGreSQL] [959] Fix an issue with the parameter() method test NULL
• [PyGreSQL] [958] trunk: Add important note regarding unnamed prepared statements NULL
• [PyGreSQL] [957] trunk: Add documentation for prepared statements NULL
• [PyGreSQL] [956] trunk: Make name in query_prepared a keyword-only parameter NULL
• [PyGreSQL] [955] trunk/pg.py: Slightly better docstrings regarding unnamed statements NULL
• [PyGreSQL] [954] trunk: Make name optional in DB methods for prepared statements NULL
• [PyGreSQL] [953] trunk: Add special methods for using prepared statements NULL
• [PyGreSQL] [952] trunk: Update PostgreSQL type definitions NULL
• [PyGreSQL] typos Justin Pryzby
  • Re: [PyGreSQL] typos D'Arcy Cain
  • Re: [PyGreSQL] typos Christoph Zwerschke
  • [PyGreSQL] typos Justin Pryzby
  • Re: [PyGreSQL] typos Justin Pryzby
  • Re: [PyGreSQL] typos Christoph Zwerschke
  • Re: [PyGreSQL] typos Justin Pryzby
  • Re: [PyGreSQL] typos Christoph Zwerschke
  • Re: [PyGreSQL] typos Justin Pryzby
  • Re: [PyGreSQL] typos Justin Pryzby
  • Re: [PyGreSQL] typos Justin Pryzby
  • Re: [PyGreSQL] typos Justin Pryzby
• [PyGreSQL] broken parsing of array bounds Justin Pryzby
  • Re: [PyGreSQL] broken parsing of array bounds Christoph Zwerschke
• [PyGreSQL] trac#16: PQexecParams resultFormat binary? Justin Pryzby
  • Re: [PyGreSQL] trac#16: PQexecParams resultFormat binary? Christoph Zwerschke
  • Re: [PyGreSQL] trac#16: PQexecParams resultFormat binary? Justin Pryzby
• [PyGreSQL] PyGreSQL #76: Support and document usage of prepared statements PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #76: Support and document usage of prepared statements PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #76: Support and document usage of prepared statements PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #76: Support and document usage of prepared statements PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #76: Support and document usage of prepared statements PyGreSQL issue tracker
• [PyGreSQL] prepared statements and EXECUTE parameters Justin Pryzby
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Justin Pryzby
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters D'Arcy Cain
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Justin Pryzby
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters D'Arcy Cain
  • [PyGreSQL] mailing lists (Re: prepared statements and EXECUTE parameters) Justin Pryzby
  • Re: [PyGreSQL] Mailman Christoph Zwerschke
  • Re: [PyGreSQL] Mailman D'Arcy Cain
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Justin Pryzby
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Justin Pryzby
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Justin Pryzby
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Justin Pryzby
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Justin Pryzby
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Justin Pryzby
  • Re: [PyGreSQL] prepared statements and EXECUTE parameters Justin Pryzby
  • [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Justin Pryzby
  • Re: [PyGreSQL] prepared statements Christoph Zwerschke
• [PyGreSQL] "TypeError: Connection is not valid" on exit from Python Jacob Champion
  • Re: [PyGreSQL] "TypeError: Connection is not valid" on exit from Python Jacob Champion
  • Re: [PyGreSQL] "TypeError: Connection is not valid" on exit from Python Christoph Zwerschke
• [PyGreSQL] [943] tags: Correction to tag name. NULL
• [PyGreSQL] [942] tags/6.0.6/: Tag version 5.0.6 NULL
• [PyGreSQL] [941] trunk/docs/contents/changelog.rst: Add release date. NULL
• [PyGreSQL] Bug in driver M P
  • Re: [PyGreSQL] Bug in driver Christoph Zwerschke
  • Re: [PyGreSQL] Bug in driver Justin Pryzby
  • Re: [PyGreSQL] Bug in driver M P
  • Re: [PyGreSQL] Bug in driver Christoph Zwerschke
  • Re: [PyGreSQL] Bug in driver M P
  • Re: [PyGreSQL] Bug in driver Christoph Zwerschke
• [PyGreSQL] [940] trunk: Prepare for version 5.0.6 NULL
• [PyGreSQL] PyGreSQL 5.0.6 and 5.1 Christoph Zwerschke
  • Re: [PyGreSQL] PyGreSQL 5.1 Christoph Zwerschke
  • Re: [PyGreSQL] PyGreSQL 5.1 D'Arcy Cain
  • Re: [PyGreSQL] PyGreSQL 5.1 Christoph Zwerschke
  • Re: [PyGreSQL] PyGreSQL 5.1 Justin Pryzby
  • Re: [PyGreSQL] PyGreSQL 5.1 Christoph Zwerschke
  • Re: [PyGreSQL] PyGreSQL 5.0.6 and 5.1 D'Arcy Cain
  • Re: [PyGreSQL] PyGreSQL 5.0.6 and 5.1 Justin Pryzby
• [PyGreSQL] PyGreSQL #75: Add autocommit option to DB API 2 PyGreSQL issue tracker
  • Re: [PyGreSQL] PyGreSQL #75: Add autocommit option to DB API 2 PyGreSQL issue tracker
• [PyGreSQL] [939] Adapt Trove classifier for the PostgreSQL license NULL
• Re: [PyGreSQL] Possible bug in PyGreSQL for Unicode and Python 2.x (Christoph Zwerschke) Murray Chapman
• [PyGreSQL] [938] The index.rst file is generated so remove from repository and ignore it. NULL
• [PyGreSQL] [937] tags/5.0.5/docs/contents/changelog.rst: Update release date in tag. NULL
• [PyGreSQL] [936] Put actual release date for 5.0.5. NULL
• [PyGreSQL] [935] tags/5.0.5/: Tag version 5.0.5. NULL
• [PyGreSQL] Possible bug in PyGreSQL for Unicode and Python 2.x Murray Chapman

• Earlier messages
• Later messages