Thanks for the tip.
Also, I disagree that the individual adapters should be stored external to
PostgreSQL. It would be trivial to set up a relation that:
1. Maintains a current list of PostgreSQL data types.
2. Maintains a list of adapters (perhaps with effective dating).
3. Maps adapters to Java types.
This would centralize the knowledge and facilitate dynamic implementations
that, for whatever reason, need to know the correct data type mapping in an
adapter-agnostic fashion. (Ideally adapters would map the PostgreSQL data
types to Java classes the same way; centralizing the list would reveal to
everyone the differences in the adapters without having to scour the web.)
This doesn't have to be packaged with PostgreSQL distributions: it could be
offered as a separate script that people can run to update the information
In response to
pgsql-novice by date
|Next:||From: Helgi Örn Helgason||Date: 2010-10-08 21:42:11|
|Subject: MySQL --> PostgreSQL with PHP|
|Previous:||From: Tom Lane||Date: 2010-10-08 16:41:49|
|Subject: Re: Unicode escape codes |