Re: DatabaseMetaData oddities

From: Kris Jurka <books(at)ejurka(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: DatabaseMetaData oddities
Date: 2003-02-04 01:24:54
Message-ID: Pine.LNX.4.33.0302032015000.27245-100000@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Tue, 4 Feb 2003, 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).
>

Arrays.sort() and Comparators

> > 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.
>

pgsql-hackers(at)postgresql(dot)org

Kris Jurka

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Matt Mello 2003-02-04 04:53:46 Re: java.lang.OutOfMemoryError
Previous Message codeWarrior 2003-02-04 00:40:51 Re: st.executeQuery("SELECT NEXTVAL('seq_suporte') AS valor");