| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: DatabaseMetaData oddities |
| Date: | 2003-02-03 21:02:56 |
| Message-ID: | 20030203210251.GB23208@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | codeWarrior | 2003-02-04 00:40:51 | Re: st.executeQuery("SELECT NEXTVAL('seq_suporte') AS valor"); |
| Previous Message | Felipe Schnack | 2003-02-03 20:50:15 | PreparedStatment.toString() |