Re: Avoiding explicit addDataType calls for PostGIS

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Markus Schaber <schabios(at)logi-track(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Avoiding explicit addDataType calls for PostGIS
Date: 2004-11-08 08:50:08
Message-ID: 418F3340.306@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-jdbc

Kris Jurka wrote:
>
>>[use a property file to configure datatypes]
>
> Looking at this patch again, I don't believe the JDBC driver should use
> this extension mechanism to configure itself. The whole concept is error
> prone with multiple .properties files,

I don't see multiple properties files with overlapping settings being a
common use case for exactly that reason.

> so why should we start things off
> by creating a properties file when we don't need to.

The configuration information is bulky, so cramming it into the URL
doesn't seem ideal.

It's also cleaner from a packaging perspective: you don't need to poke
application-specific internal configuration information into a
user-visible or user-configured URL.

-O

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dawid Kuroczko 2004-11-08 08:50:20 Re: Postresql RFD version 2.0 Help Wanted.
Previous Message Brian {Hamilton Kelly} 2004-11-08 08:41:56 Re: Postresql RFD version 2.0 Help Wanted.

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2004-11-08 09:02:36 Re: Avoiding explicit addDataType calls for PostGIS
Previous Message Kris Jurka 2004-11-08 08:37:17 Re: Avoiding explicit addDataType calls for PostGIS