Patches applied Re: DatabaseMetaData oddities - Mailing list pgsql-jdbc

From Dave Cramer
Subject Patches applied Re: DatabaseMetaData oddities
Date
Msg-id 1044355534.1122.2.camel@inspiron.cramers
Whole thread Raw
In response to Re: DatabaseMetaData oddities  (Oliver Jowett <oliver@opencloud.com>)
List pgsql-jdbc
The jdbc3 patch was applied by me, and Barry applied the toString patch

Thanks,
Dave
On Mon, 2003-02-03 at 16:02, Oliver Jowett wrote:
> On Mon, Feb 03, 2003 at 01:00:11PM -0500, Kris Jurka wrote:
>
> > The getTypeInfo patch uses functionality not in Java 1.1 so it cannot be
> > used in the jdbc1 package.
>
> I'll look at revising this shortly. What specifically isn't available in 1.1
> that the patch used? (the JDK javadoc is fairly useless at giving an
> overview of API changes by version).
>
> > The getMaxTableNameLength patch is not a good idea.  You're changing
> > something general to fix a very specific problem.  I would recomend using
> > explicit constraint names or petitioning backend developers to create
> > non-conflicating auto generated names.
>
> Certainly the best fix is to fix the backend.. Where's the best place to
> forward this to? I doubt I'll have time to work on this myself.
>
> In the meantime I'll probably use an explicitly named constraint as you
> suggest, but this is likely to bite anyone using the metadata values to
> generate unique table names.
>
> -O
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
--
Dave Cramer <Dave@micro-automation.net>


pgsql-jdbc by date:

Previous
From: Barry Lind
Date:
Subject: Re: DatabaseMetaData oddities
Next
From: Dave Cramer
Date:
Subject: Patch Applied question about rollback and SQLException