Re: Avoiding explicit addDataType calls for PostGIS

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

Markus Schaber wrote:

>>Perhaps an array-based accessor, one element per datatype?
>
> Or a Map, so we can index via name.

This doesn't play so well with JavaBeans. It has mechanisms for handling
array-based accessors, but a Map is just a serializable object..

>>Alternatively, collapse all the datatype stuff down to a single property
>>and teach the property-munging code how to merge (rather than replace)
>>multiple settings of that property together. (this second option is more
>>like what JNDI property files do)
>
> This sounds cleaner, IMHO. This would produce (and allow) to specify
> something like datatypes=geom:org.postgis.PGgeometry,blubb=com.foo.bar
>
> Should I try to change the patch this way?

If you have time that'd be appreciated. I'm short on time and recovering
from illness right now :(

-O

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Franco Bruno Borghesi 2004-11-03 20:08:51 Re: Number of months
Previous Message Jeff Bohmer 2004-11-03 20:02:12 Re: PostgreSQL on Linux PC vs MacOS X

Browse pgsql-jdbc by date

  From Date Subject
Next Message Oliver Jowett 2004-11-03 20:12:56 Re: 8.0.0beta4: "copy" and "client_encoding"
Previous Message Kris Jurka 2004-11-03 19:42:36 Re: 8.0.0beta4: "copy" and "client_encoding"