| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
class name for a byte[]
|
|
|
|
was submitted by Paul Bethe pmbethe@yahoo.com
|
|
(forth@mail.net.tw)
|
|
ResultSetMetaData.getColumnClassName() support
|
|
timestamps which do not have timezone info were being interpreted in local timezone instead of GMT. Also added a check to support timestamp vs. timestamptz in this code
|
|
|
|
|
|
|
|
|
|
|
|
|
|
execute
|
|
|
|
to read the underlying data into rowbuffer
|
|
|
|
Allows you to set the loglevel at runtime by adding ?loglevel=X to the connection URL, where 1 = INFO and 2 = DEBUG.
Automatically turns on logging by calling DriverManager.setPrintWriter(new PrintWriter(System.out)) if one is not already set.
Adds a Driver.info() message that prints out the version number
Adds member variables logDebug and logInfo that can be checked before making logging methods calls
Adds a build number to the version number string. This build number will need to be manually incremented when we see fit.
----------------------------------------------------------------------
Modified Files:
org/postgresql/Connection.java org/postgresql/Driver.java.in
org/postgresql/fastpath/Fastpath.java
org/postgresql/jdbc1/DatabaseMetaData.java
org/postgresql/jdbc2/Connection.java
org/postgresql/jdbc2/DatabaseMetaData.java
org/postgresql/largeobject/LargeObjectManager.java
org/postgresql/util/PSQLException.java
org/postgresql/util/Serialize.java
----------------------------------------------------------------------
|
|
Integer for a smallint datatype instead of a Short
|
|
|
|
of keys
|
|
handled Timestamps incorrectly
|
|
|
|
|
|
GUC support. It's now possible to set datestyle, timezone, and
client_encoding from postgresql.conf and per-database or per-user
settings. Also, implement rollback of SET commands that occur in a
transaction that later fails. Create a SET LOCAL var = value syntax
that sets the variable only for the duration of the current transaction.
All per previous discussions in pghackers.
|
|
The code was not expecting to receive notice messages during the connection handshake.
|
|
Zhenbang Wei
|
|
|
|
added a setup/teardown to create and drop the connection, and table
|
|
repaired the bug, haven't made it caseInsensitive
|
|
problem reported a few months ago where a select in a rule was causing an insert statement to return a result set which the code was explicitly prohibiting.
|
|
also fixed a NPE when calling the next() method on a result set after the
connection or resultset has been closed. (bug reported by Hans Deragon)
|
|
support
|
|
Fixed NPE when database name was not passed on the jdbc connection URL
Fixed Connection.isClosed() to not hit the DB for every call
|
|
these versions adhere to the backend protocol better than previous version
fixes problem when an error occurs on the backend, and the connection is still used
previous versions were throwing an exception half way through the protocol, leaving it
indeterminate.
also removes empty query code, should speed things up a bit
|
|
QueryExecutor. This includes:
1) only exit after we receive a 'Z' packet
2) append error messages to a buffer and throw the exception at the end
|
|
|
|
StartupPacket
* Introduces a new class, StartupPacket.
* Moves a lot of constants from Connection to StartupPacket.
* Makes two instance variables in Connection into locals.
|
|
> Korean (JOHAB), Thai (WIN874),
> Vietnamese (TCVN), Arabic (WIN1256)
>
>Added ClientEncoding
> Simplified Chinese (GBK), Korean (UHC)
>
>Add PsqlODBC and document ...etc patch.
"JDBC patch" is delivered, too. :-)
Eiji Tokuya
|
|
If one is trying to compile a JDBC 1 driver and junit.jar is in the
CLASSPATH, then the build fails as ant tries to build the JDBC 2 test
classes. This patch fixes this problem by excluding the jdbc 2 files
unless the jdk1.2+ property is set.
|
|
code before QueryExecutor class was created and copied behaviour
|
|
previously it was throwing a SQLException as soon as the error message was
received from the backend. This did not allow the protocol to finish properly
now, simply collects error messages from the backend until the query is done
and throws exception at the end
Also added setLogLevel to Driver.java, and made the log levels public
|
|
This patch solve problems with arrays in latest development JDBC driver
|
|
moved the check for columnIndex into same call
check at the top of all getXXX
added appropriate error
|
|
driver. PSQLExceptions are thrown instead of SQLExceptions and if a warning is received while waiting for the backend secret key, that warning is chained to the new Connection object instead of generating an exception. A couple new error messages have been added.
|
|
|
|
|
|
and ResultSet
|
