thx, will be removed then. do you know that it is good for anyway?
..ede
On 28.12.2015 20:00, Larry Reeder wrote:
> Ede, no I don't need postgis-stubs.
>
> Thanks..lreeder
>
> On Mon, Dec 28, 2015 at 9:57 AM, wrote:
>
>> On 28.12.2015 16:07, Larry Reeder wrote:
>>> DBQuery use
Ede, no I don't need postgis-stubs.
Thanks..lreeder
On Mon, Dec 28, 2015 at 9:57 AM, wrote:
> On 28.12.2015 16:07, Larry Reeder wrote:
> > DBQuery uses PGGeometry from the PostGIS package to parse the PostGIS
> > geometries, and so does require postgis jars. However, removing
On 28.12.2015 16:07, Larry Reeder wrote:
> DBQuery uses PGGeometry from the PostGIS package to parse the PostGIS
> geometries, and so does require postgis jars. However, removing postgis
> JAR dependencies from OJ makes sense if OJ isn't using it, and I can just
> repackage it in the DbQuery plug
DBQuery uses PGGeometry from the PostGIS package to parse the PostGIS
geometries, and so does require postgis jars. However, removing postgis
JAR dependencies from OJ makes sense if OJ isn't using it, and I can just
repackage it in the DbQuery plugin. Since PG is so well supported in the
baseli
Hi Ede,
I think that PostGIS driver for datastore framework only needs
postgresql-jdbc-driver (+jts)
but dbquery from Larry needs postgresql-jdbc-driver + postgis.
Not sure of that though.
It would make sense to move potgresql-jdbc-driver to PLUS, as other
drivers, but it will probably break some
hey Mike & All,
1.
currently we have,
postgresql (644kB) in CORE
postgis (78kB) in PLUS
which makes no sense to me. can we move both to either CORE or PLUS?
2.
there is a lib/plus/postgis-stubs-*.jar which looks like it just contains
obsolete postgresql stubs. do we really need it? what for?
