Re: [Geotools-gt2-users] Permission Denied Error on a PostGIS Query

[Ben Caradoc-D. <Ben...@cs...>]

Thanks, Gerson. I can now confirm Andrea's advice that this is just a 
warning (with a typo) on trunk and 2.7.1. I have tested this using 
GeoServer (GeoTools trunk) and I get the same warning that you see on 
2.7.1. The warning is logged, but the plugin falls back to using 
geometry_columns and geometries are created correctly.

Thanks for taking the time to confirm this behaviour.

Kind regards,
Ben.

On 01/06/11 07:11, Gerson Galang wrote:
> Hi Ben, Andrea,
>
> I followed your suggestion of cleaning up my eclipse project workspace
> but it still didn't fix the problem I reported originally. I'm still
> getting a warning message if I change the ownership of the
> geography_columns to 'postgres'
>
> Jun 1, 2011 9:04:20 AM org.geotools.data.postgis.PostGISDialect
> getGeometrySRID
> WARNING: Failed to retrieve information about
> public.lga07aaust_region.wkb_geometry from the geometry_columns table,
> checking geometry_columns instead
> org.postgresql.util.PSQLException: ERROR: permission denied for relation
> geography_columns
>
> But the clean eclipse project workspace has fixed the issue with 2.7.1
> complaining about CQLException not being thrown by CQL.toFilter() method.
>
> Cheers,
> Gerson
>
>
> On 05/27/2011 05:01 PM, Ben Caradoc-Davies wrote:
>> On 27/05/11 10:34, Gerson Galang wrote:
>>> I had a go at 2.7.1 yesterday but it started complaining about the
>>> parameter I'm trying to pass to the DataStoreFinder. I just get a null
>>> value when I instantiate the DataStore.
>>
>> Do you have an old gt-postgis on your classpath? There is some funny
>> logic in gt-jdbc-postgis that gives gt-postgis preference if both are
>> present and you use dbtype=postgis (for backwards compatibility). But
>> this should not happen if you are using Maven.  :-(
>>
>> Perhaps the step below might help this too:
>>
>>> Another weird thing I've noticed is that the CQL.toFilter doesn't throw
>>> a CQLException anymore on 2.7.1. Even if the documentation states that
>>> it throws a CQLException, Eclipse just complains about my try-catch
>>> block not having any statement that throws a CQLException.
>>
>> Please try:
>> mvn eclipse:clean eclipse:eclipse
>> and then refresh and then clean your project in Eclipse. Sometimes
>> Eclipse falls down and can't get up.  :-P
>>
>

-- 
Ben Caradoc-Davies <Ben...@cs...>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre