• Text Size: Normal / Large
• Donate
• Contact

Section Navigation

• Community
• Contributors
• Mailing Lists
  • Subscribe
  • User lists
    • pgsql-admin
    • pgsql-advocacy
    • pgsql-announce
    • pgsql-bugs
    • pgsql-docs
    • pgsql-cygwin
    • pgsql-general
    • pgsql-interfaces
    • pgsql-jdbc
    • pgsql-jobs
    • pgsql-novice
    • pgsql-odbc
    • pgsql -performance
    • pgsql-php
    • pgsql-ports
    • pgsql-sql
  • Developer lists
  • Regional lists
  • Project lists
  • User groups
  • Inactive lists
• IRC
• Featured Users
• International Sites
• Propaganda
• Resources
• Weekly News
• Community login
  • Profile
  • Lost password

pgsql-jdbc 2008-05 Chronological Index (1/1)

• Thread Index
• [Prev Page]
• [Next Page]

• 29 May 2008
  • Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work Tom Lane
  • Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work Jignesh K. Shah
  • Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work Jignesh K. Shah
• 28 May 2008
  • Re: ResultSet & setFetchSize fails to stop heap failures Kris Jurka
  • Re: ResultSet & setFetchSize fails to stop heap failures U. George
  • Re: ResultSet & setFetchSize fails to stop heap failures Kris Jurka
  • ResultSet & setFetchSize fails to stop heap failures U. George
  • Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work Tom Lane
  • Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work Dave Cramer
• 23 May 2008
  • Re: How embarrassing: optimization of a one-shot query doesn't work Tom Lane
  • Re: How embarrassing: optimization of a one-shot query doesn't work Dave Cramer
• 21 May 2008
  • Types of SQL statements swallowed by PG's engine Albretch Mueller
  • Re: Feature Request: PSQLException verbosity option Daniel Migowski
  • Re: org.postgresql.xa.PGXADataSource and compatible=8.2 in query string Kris Jurka
  • Re: org.postgresql.xa.PGXADataSource and compatible=8.2 in query string Achilleas Mantzios
• 20 May 2008
  • Re: Feature Request: PSQLException verbosity option Kris Jurka
  • Re: org.postgresql.xa.PGXADataSource and compatible=8.2 in query string Kris Jurka
  • Re: Updated head revision translation (German) Kris Jurka
  • Re: Updated head revision translation (German) Andre Bialojahn
  • Re: org.postgresql.xa.PGXADataSource and compatible=8.2 in query string Achilleas Mantzios
  • Re: org.postgresql.xa.PGXADataSource and compatible=8.2 in query string Achilleas Mantzios
  • Re: org.postgresql.xa.PGXADataSource and compatible=8.2 in query string Achilleas Mantzios
  • org.postgresql.xa.PGXADataSource and compatible=8.2 in query string Achilleas Mantzios
  • Re: Feature Request: PSQLException verbosity option Daniel Migowski
  • Re: Couple of preparedstatement bug suspects Kris Jurka
  • Re: Two BLOBs (OID) in table? Kris Jurka
  • Re: Feature Request: PSQLException verbosity option Kris Jurka
  • Re: SET client_encoding = 'UTF8' Kris Jurka
  • Re: German translation fixes Kris Jurka
  • Re: Updated head revision translation (German) Kris Jurka
• 19 May 2008
  • Re: SET client_encoding = 'UTF8' Kris Jurka
  • Re: SET client_encoding = 'UTF8' Tom Lane
  • Re: SET client_encoding = 'UTF8' Oliver Jowett
  • Re: SET client_encoding = 'UTF8' Tom Lane
  • Re: SET client_encoding = 'UTF8' Daniel Migowski
• 18 May 2008
  • Re: SET client_encoding = 'UTF8' Oliver Jowett
  • Re: SET client_encoding = 'UTF8' Kris Jurka
  • Re: SET client_encoding = 'UTF8' Tom Lane
  • SET client_encoding = 'UTF8' Daniel Migowski
• 15 May 2008
  • Re: Testing JDBC Prepared Statements Daniel Migowski
  • Re: scrollable ResultSet advise Achilleas Mantzios
  • Re: Not fetching the entire result set when using holdable cursors Kris Jurka
  • Re: scrollable ResultSet advise Kris Jurka
• 14 May 2008
  • Not fetching the entire result set when using holdable cursors Arie Ozarov
  • Re: Testing JDBC Prepared Statements Kris Jurka
  • Testing JDBC Prepared Statements Daniel Migowski
  • Re: 25P02, current transaction is aborted, commands ignored Albe Laurenz
• 13 May 2008
  • Re: 25P02, current transaction is aborted, commands ignored Dave Cramer
  • Re: 25P02, current transaction is aborted, commands ignored sangeetha
• 12 May 2008
  • scrollable ResultSet advise Achilleas Mantzios
  • Re: Correct getScale() behavior? tivvpgsqljdbc
  • Re: JDBC types vs postgres types correspondation Kris Jurka
  • Re: Couple of preparedstatement bug suspects Kris Jurka
• 10 May 2008
  • JDBC types vs postgres types correspondation Marco Solinas
  • Re: Correct getScale() behavior? Tom Lane
• 09 May 2008
  • Re: Correct getScale() behavior? Kris Jurka
  • Re: Couple of preparedstatement bug suspects Kris Jurka
  • Re: Correct getScale() behavior? dombrd
  • Re: Couple of preparedstatement bug suspects Roy Smith
  • Re: Couple of preparedstatement bug suspects Kris Jurka
  • Couple of preparedstatement bug suspects Roy Smith
• 08 May 2008
  • Re: Correct getScale() behavior? Kris Jurka
  • Re: JDBC and GSSAPI/Krb5 with uDig Kris Jurka
• 07 May 2008
  • German translation fixes Peter Eisentraut
  • Re: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend Albe Laurenz *EXTERN*
  • Re: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend Albretch Mueller
  • Re: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend Albe Laurenz *EXTERN*
  • Re: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend Albretch Mueller
  • org.postgresql.util.PSQLException: An I/O error occured while sending to the backend Albretch Mueller
• 06 May 2008
  • JDBC and GSSAPI/Krb5 with uDig Stephen Frost
• 05 May 2008
  • Correct getScale() behavior? Dave Dombrosky
  • Re: ERROR: insufficient data left in message Daniel Migowski
  • Re: invalid message format and I/O error while comunicating with backend Sergi Vera
• 01 May 2008
  • Re: BLOB is read into memory instead of streaming (bug?) robert engels
  • Re: BLOB is read into memory instead of streaming (bug?) Kris Jurka
  • Re: BLOB is read into memory instead of streaming (bug?) robert engels

• Thread Index
• [Prev Page]
• [Next Page]