Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[udig-devel] [jira] Created: (UDIG-624) postgis driver causes null with use of schema's 
postgis driver causes null with  use of schema's
------------------------------------------------

         Key: UDIG-624
         URL: http://jira.codehaus.org/browse/UDIG-624
     Project: uDIG
        Type: Sub-task
  Components: postgis  
    Versions: UDIG 1.0.4    
 Environment: postgis 1.0 postgresql 8 udig 1.0.5 (!)
 Reporter: Floris Sluiter
 Assigned to: Jody Garnett 
    Priority: Critical
 Attachments: postgis_errors.txt, ss1.png, ss2.png

 I have postgresql 7.4 and 8.0 installed on the same debian server, each
on its own port 5432 and 5433. Both installations have a perfectly OK
working postgis installation (0.9 and 1.0).

Now I can connect with udig (from windows) to the pg7.4pgis0.9
installation and display the tables.

When I try to connect to the 8.0 installation it fails with message
'error while installing service'

The strange thing is, that it does connect to the database at first and it
does display the schema's that I use to subdivide my maps. However trying
to view the data fails with the above error message. A second attempt to
connect gave an error report.

I attached a document with the relevant 40 lines from the error.log and a
copy/paste from the java exception output.

And two screenshots that show my database set-up.
Note that in the 7.4 version on port 5432 I have the tables all in the
public schema, however in the 8.0 version I have only the geometry_columns
and spatial_ref_sys in the public schema, the tables with shapefiles are
ordered thematically and have there own schemas.

Hope this helps, otherwise I can provide more info

Regards,

Floris

Comment by Jody Garnett:
Bug #2 - this one should go to the devel list, but I will ask that you 
mention what version of uDig you are using? We recently created uDig 
1.0.5 (but I have not seen it announced yet). Justin has also been 
applying several fixes to PostGIS as part of his efforts to release 
GeoServer. My guess is we may need to update the jdbc driver we use. If 
your postgis is public we should be able to set up a test case to 
reproduce the problem (as we do not have access to a debian server as 
far as I know).

Additional comment by Floris:
I use udig 1.0.5.
I agree that it probably lies in the jdbc driver that doesn't work well with schema's (see attached screenshot for my postgis setup.
The data that I have in the postgis database is not open, if we need to setup a testcase here, I'll have to do that manually in a separate database, but that can be done. However, I do not think it is a debian problem, I think it is the schema's that cause the problem.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Back to the top