74 messages

org.postgresql.pgsql-jdbc [All Lists]

2008 May [All Months]

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