RH8/7.2.2 Test Suite Problem - Mailing list pgsql-jdbc

On 11 Dec 2002, Dave Cramer wrote:
> Patch applied!

    Thanks.

> The test suite doesn't fail on my machine using a 7.3 backend??

    I have two Red Hat 8 machines with the default PG install (7.2.2).
Both fail the same item in the test suite.  Does anyone else have a Red
Hat 8 (or PG 7.2.2) box they can run the test suite against to check this?
    Also, Dave, do you have some other tables in the test database so
we're sure that the correct table isn't the first table listed just by
coincidence?  Perhaps we should adjust the setUp and tearDown for the
DatabaseMetaDataTest class to create table 'aaa' before 'testmetadata',
and 'zzz' after 'testmetadata', just to be sure.
    In fact, I've attached a patch for
org.postgresql.test.jdbc2.DatabaseMetaDataTest to do that.  Note there's
an extra println right before where I get the failure, and when I run the
patched test, it prints "TABLE NAME = aaa" despite the "testmetadat%"
criterion.

Thanks,
    Aaron

[junit] There was 1 failure:
[junit] 1) testTables(org.postgresql.test.jdbc2.DatabaseMetaDataTest)junit.framework.AssertionFailedError
[junit]     at org.postgresql.test.jdbc2.DatabaseMetaDataTest.testTables(DatabaseMetaDataTest.java:55)
[junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

When I put in some debugging output, this line gets the table name from
the ResultSet, which returns the name of the first table in the DB
(apparently alphabetically) instead of a table name matching the selection
criteria passed in ("testmetadat%").

Aaron