Re: RH8/7.2.2 Test Suite Problem

test=> \d
      List of relations
    Name     | Type  | Owner
-------------+-------+-------
 bar         | table | test
 foo         | table | test
 jmsjmsstate | table | test
 jmsjmsstore | table | test
(4 rows)


    With the CVS version of the test, I get "foo" instead of
"testmetadata".  When I patched the test to create "aaa" and "zzz" as
well, the method was getting "aaa" instead of "testmetadata" or any of the
tables listed here.

Aaron

On 11 Dec 2002, Dave Cramer wrote:
> Aaron,
>
> What other tables do you have in the database?
>
> mine has
> psql test
> \d
>              List of relations
>  Schema |      Name      |   Type   | Owner
> --------+----------------+----------+-------
>  public | FOO            | table    | davec
>  public | address        | table    | davec
>  public | foo            | table    | davec
>  public | foo_id_seq     | sequence | davec
>  public | issue_priority | table    | davec
>  public | issue_status   | table    | davec
>  public | person         | table    | davec
>  public | person_role    | table    | davec
>  public | project        | table    | davec
>  public | role           | table    | davec
> (10 rows)
>
>
> Dave
> On Wed, 2002-12-11 at 10:05, Aaron Mulder wrote:
> > 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
> >
> > ______________________________________________________________________
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
> >
> > http://archives.postgresql.org
>