I am trying to retrieve information about the structure of the database
using the DatabaseMetadata class. I am using version 7.1.3 and the latest
JDBC Drivers I can find. I got similar results with the versions supplied
with Mandrake 8.0 (7.0.3 and associated drivers)
The problems are:
1.
On Thu, 6 Sep 2001 22:30:58 +0100, you wrote:
The problems are:
1. No Index information from the getIndexInfo method
Hmmm... looking at the source, it apppears that
DatabaseMetaData.getIndexInfo() is implemented. If it doesn't
work for you, we would need more information about the problem
to be
we use a hashtable with connections as keys and timestamps as values...we do
that so that we can clean up connections that haven't been used in a
while...i know that some DBs invalidate their connections after a certain
amount of time, so we have a process that periodically walks through the
Rene Pijlman [EMAIL PROTECTED] writes:
Reading the book Understanding the SQL standard it seems that
what the standard calls a schema is a database in PostgreSQL. A
catalog is a set of schemas. Following the standard, a session
is supposed to have access to a catalog, but in PostgreSQL it
The ConnectionTest test case in our own jdbc2 test suite fails
to set and get the transaction isolation level correctly. After
looking at the implementation I've come to the conclusion that
the test case itself is flawed, but I wanted to check my
conclusion with this list.
What the test case
Rene,
I've attached some sample code, the script I use for creating the database,
and the output when I run it here:
I am sorry, but I didn't notice the Null Pointer Exception being produced
by the getIndexInfo method. It doesn't seem to matter whether I supply a
table name, schema name
On Fri, 07 Sep 2001 10:12:39 +0200, I wrote:
getColumns() was fixed recently. It returned only columns with a
comment (IIRC).
No, it returned only columns with a default value, according to
Jeroen van Vianen who fixed it (in 7.2).
See http://fts.postgresql.org/db/mw/msg.html?mid=1032468
Patch applied. Thanks.
Attached is a patch that fixes 2 test cases of the JDBC test
suite. This reduces the number of failures from 9 to 7.
Both ConnectionTest and JBuilderTest did not create their own
tables, which caused these test cases to fail with relation ...
does not exist. It
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Dave Cramer
Sent:
Thanks for the votes of confidence. I am willing to take on the
responsibility if the core committee agrees.
Yes, we do. We don't know Java very well and are struggling. It would
be nice to have someone who actually know the language applying the
patches. :-)
--
Bruce Momjian
At 00:30 9/7/2001 -0400, Bruce Momjian wrote:
Can someone tackles this and supply a patch?
This has been addressed in the patch that was recently committed for JDBC's
broken getColumn() support. As I'm using outer joins and was unable to come
up with SQL syntax that would correctly use an
Your recommendation to leave the behavior as is and change the
regression test is fine with me.
thanks,
--Barry
Rene Pijlman wrote:
The ConnectionTest test case in our own jdbc2 test suite fails
to set and get the transaction isolation level correctly. After
looking at the implementation
Can I have a new version of this for application?
Dave Harkness wrote:
At 12:41 PM 9/5/2001, Joseph Shraibman wrote:
new patch:
There still seems to be an error with the same if-block.
! if (index=-rows.size())
! internalIndex=rows.size()+index;
I have added this to the jdbc source tree as TESTSUITE.
Bruce,
I posted this a couple of days ago on pgsql-patches and haven't
seen a reply, and if I'm not mistaken the file is not in current
CVS.
Maybe my posting was overlooked.
-+-+-
I've written a brief Howto document about
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
Barry Lind wrote:
Joseph,
In looking at this patch it looks OK, except for the following change:
!
15 matches
Mail list logo