• 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 Thread Index (1/1)

• Main Index
• [Prev Page]
• [Next Page]

• 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 Tom Lane
• Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work Jignesh K. Shah
• ResultSet & setFetchSize fails to stop heap failures U. George
• 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
• Re: How embarrassing: optimization of a one-shot query doesn't work Dave Cramer
• Re: 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
• Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work Tom Lane
• Types of SQL statements swallowed by PG's engine Albretch Mueller
• 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
• 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 Kris Jurka
• 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 Kris Jurka
• Re: Two BLOBs (OID) in table? Kris Jurka
• Re: Feature Request: PSQLException verbosity option Kris Jurka
• Re: Feature Request: PSQLException verbosity option Daniel Migowski
• Re: Feature Request: PSQLException verbosity option Kris Jurka
• Re: Feature Request: PSQLException verbosity option Daniel Migowski
• Re: Updated head revision translation (German) Kris Jurka
• Re: Updated head revision translation (German) Andre Bialojahn
• Re: Updated head revision translation (German) Kris Jurka
• SET client_encoding = 'UTF8' Daniel Migowski
• Re: SET client_encoding = 'UTF8' Tom Lane
• Re: SET client_encoding = 'UTF8' Oliver Jowett
• Re: SET client_encoding = 'UTF8' Kris Jurka
• Re: SET client_encoding = 'UTF8' Daniel Migowski
• 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' Kris Jurka
• Re: SET client_encoding = 'UTF8' Kris Jurka
• Not fetching the entire result set when using holdable cursors Arie Ozarov
• Re: Not fetching the entire result set when using holdable cursors Kris Jurka
• Testing JDBC Prepared Statements Daniel Migowski
• Re: Testing JDBC Prepared Statements Kris Jurka
• Re: Testing JDBC Prepared Statements Daniel Migowski
• Re: 25P02, current transaction is aborted, commands ignored sangeetha
• Re: 25P02, current transaction is aborted, commands ignored Dave Cramer
• Re: 25P02, current transaction is aborted, commands ignored Albe Laurenz
• scrollable ResultSet advise Achilleas Mantzios
• Re: scrollable ResultSet advise Kris Jurka
• Re: scrollable ResultSet advise Achilleas Mantzios
• JDBC types vs postgres types correspondation Marco Solinas
• Re: JDBC types vs postgres types correspondation Kris Jurka
• Couple of preparedstatement bug suspects Roy Smith
• Re: Couple of preparedstatement bug suspects Kris Jurka
• Message not available
  • Re: Couple of preparedstatement bug suspects Roy Smith
  • Re: Couple of preparedstatement bug suspects Kris Jurka
  • Re: Couple of preparedstatement bug suspects Kris Jurka
  • Message not available
    • Message not available
      • Re: Couple of preparedstatement bug suspects Kris Jurka
• German translation fixes Peter Eisentraut
• Re: German translation fixes Kris Jurka
• 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 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
• Re: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend Albe Laurenz *EXTERN*
• JDBC and GSSAPI/Krb5 with uDig Stephen Frost
• Re: JDBC and GSSAPI/Krb5 with uDig Kris Jurka
• Correct getScale() behavior? Dave Dombrosky
• Re: Correct getScale() behavior? Kris Jurka
• Re: Correct getScale() behavior? dombrd
• Re: Correct getScale() behavior? Kris Jurka
• Re: Correct getScale() behavior? Tom Lane
• Re: Correct getScale() behavior? tivvpgsqljdbc
• Re: ERROR: insufficient data left in message Daniel Migowski
• Re: invalid message format and I/O error while comunicating with backend Sergi Vera
• 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

---

• Main Index
• [Prev Page]
• [Next Page]

---

Mail converted by MHonArc