This has not been fixed. Currently the driver is doing something along
the lines of
" WHERE c.relname LIKE " + tableNamePattern.toLowerCase();
This masks the problem of a user supplying an uppercase version of a
tablename that was case folded to lower, but does not work when they
really want an uppercase table name.
I believe that adding a LOWER() to c.relname is the best temporary
solution until we figure out a better way to handle case sensitivity.
Barry, If you believe this is the way to go I will work up a patch for
this an similar places in the driver.
Kris Jurka
On Tue, 29 Oct 2002, Barry Lind wrote:
> Wolfgang,
>
> Can you try this test using the 7.3beta3 build of the driver from
> jdbc.postgresql.org? I think this should be fixed in the latest build.
>
> thanks,
> --Barry
>
>
> w.winter wrote:
> > Hi,
> >
> > on testing our auto-configuration persistence framework ACP against
> > PostgreSQL we found the following problem:
> >
> > There is a table A625431658_Person1, created as quoted mixed case
> > identifier.
> >
> > I do:
> > databaseMetaData.getTables(null, null, "%", new String[] {"TABLE"})
> > --> A625431658_Person1 is in the ResultSet. OK.
> >
> > I do:
> > databaseMetaData.getTables(null, null, "A625431658_Person1", new String[]
> > {"TABLE"})
> > --> A625431658_Person1 is NOT in the ResultSet.
> >
> > I do:
> > databaseMetaData.getTables(null, null, "%erson1", new String[] {"TABLE"})
> > --> A625431658_Person1 is in the ResultSet. OK.
> >
> > Seems there is a problem with mixed case ?
> >
> >
> > Wolfgang
> >
> > ___________________
> > Dr. Wolfgang Winter
> > LogiTags Systems
> > www.logitags.com
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
> >
> > http://archives.postgresql.org
> >
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>