Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Rene Pijlman writes:
>> Currently the JDBC driver says:
>> - Backend >= 7.2 sorts nulls higher than any other value in a
>> domain. In other words: ascending means nulls at the end,
>> descending means nulls at the start.
>> - Backend < 7.2 puts nulls
Attached is a patch that fixes ResultSetMetaData.isNullable() in
the JDBC driver.
This method is currently unimplemented and always returns
ResultSetMetaData.columnNullable. This is obviously incorrect
when a column is defined with NOT NULL or PRIMARY KEY. And we
have to think of check constraint
On Fri, 14 Sep 2001 17:53:50 +0200, you wrote:
>could someone tell me, please, do I have any chance to get
>proper implementation of above method in JDBC (1.1+) soon?
This is a volunteer project. You don't "get", you "bring" :-)
>Current "return 1" works fine on most tables, however it seems
>to
Hi all,
I'm doing some research into tightly coupling data mining applications to
PostgreSQL, and have a couple of questions:
1) What's the default fetch size set by the jdbc driver (jdbc7.0-1.2.jar)?
2) Is there any way to change this other than by editing the source code?
The setFetchSize and
Hello,
I have, for some time, now, been working on the updateable resultset
class. Please have a look at http://www.miranda.org/~ola/jdbcupr.diff, and
let me know what you think. It is only rudimentary at the moment.
Things to consider:
* Parsing of query. Very hackish at the moment.
* Concurre
