Re: [Geotools-gt2-users] epsg in postgres 8.3.1

[Jody G. <jga...@re...>]

Mark Leslie wrote:
> "Previously, if a non-character value was supplied to an operator or
> function that requires text input, it was automatically cast to text,
> for most (though not all) built-in data types. This no longer happens:
> an explicit cast to text is now required for all non-character-string
> types."
>
> It looks like we need to update some of our queries.  You may be able
> to work around this for the moment by redefining the integer -> text
> cast as implicit.  See
> http://www.postgresql.org/docs/8.3/interactive/sql-createcast.html.
>   
Agreed; the class used is here:

The FactoryUsingAnsiSQL should be used; I don't think we need a Postgres 
specific subclass; but you can check out how FactoryUsingOracleSQL and 
FactoryUsingHSQL does things.

The Idea here is a one two punch:
- punch 1: ThreadedPostgresSQLEpshFactory keeps a pool of connections to 
your database for scalability; and keeps a cache of results around
- punch 2: A pool of FactoryUsingSQL subclass grab the definitions from 
the database as needed to keep ThreadedPostgresSQLFactory happy

Cheers,
Jody