Re: Avoiding explicit addDataType calls for PostGIS
От | Oliver Jowett |
---|---|
Тема | Re: Avoiding explicit addDataType calls for PostGIS |
Дата | |
Msg-id | 418939E6.7030602@opencloud.com обсуждение исходный текст |
Ответ на | Re: Avoiding explicit addDataType calls for PostGIS (Markus Schaber <schabios@logi-track.com>) |
Ответы |
Re: Avoiding explicit addDataType calls for PostGIS
|
Список | 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
В списке pgsql-jdbc по дате отправления: