gvSIG bugs #1451

connection to postgis fails - missing geodb manager

Added by Klaus Schaefer over 11 years ago. Updated about 10 years ago.

Status:Closed% Done:

0%

Priority:UrgentSpent time:-
Assignee:Juan Lucas Domínguez
Category:Database
Target version:2.0.0-rc2
Severity: Add-on version:
gvSIG version:2.0.0 Add-on build:
gvSIG build:2060 Add-on resolve version:
Operative System:Windows Add-on resolve build:
Keywords:postgis connection geodb Proyecto:
Has patch:No Hito:
Add-on name:Unknown

Description

All attemps to connect to postgis fail. How do the parameters need to be specified, compared to previous versions (1.11/1.12)? The geodb manager is missing, no selection of existing connections possible. The GUI interface for specifying db connections is not translated into english language.

gvSIG_2_0_postgres_error.log - gvSIG log file (35.1 KB) Klaus Schaefer, 12/04/2012 02:35 PM

conn_example.jpg (82.6 KB) Juan Lucas Domínguez, 12/05/2012 11:41 AM

gvSIG.log (141 KB) Klaus Schaefer, 12/10/2012 09:24 AM

gvSIG1-2-0-postgis-issue.pdf (125 KB) Klaus Schaefer, 12/10/2012 09:24 AM

441

History

#1 Updated by Juan Lucas Domínguez over 11 years ago

  • File conn_example.jpg added
  • Status changed from New to Awaiting response
  • Assignee set to Juan Lucas Domínguez

Added translations ( gvsig-desktop:r39398 ). They will be available in gvSIG 2.0.0 2061

Hello Klaus,
I have used a PostGIS connection correctly.
Your log file says that the host is unknown (in theory, it's a wrong IP or wrong host name)

You can see an image attached that shows how to use the dialogs (conn_example.jpg). The "connections manager" is not available in gvSIG 2.0.0 but there is not much difference. Connections are opened and closed as the application needs them.

Where you able to connect to that host from gvSIG 1.12 or from another application?

#2 Updated by Joaquín del Cerro Murciano over 11 years ago

  • Target version changed from 2.0.0-rc1 to 2.0.0-final

#3 Updated by Klaus Schaefer over 11 years ago

Hello Juan,

thanks a lot!!! I could now connect successfully!

However, I usually used to restrict the SQL with the syntax "where cc_east notnull and cc_east > 0". In 1.11 and 1.12 this workes fine. In 2.0 it does not work, no data is returned. At the first try I received an error message and no rows were returned. Repeating the action again just returned no rows, without error message.

Without SQL-restriction the adding of the geodb layer works fine!

Can you have a look at it? Log file and screensho attached.

Thanks a lot!
Klaus

#4 Updated by Klaus Schaefer over 11 years ago

I just looked a little bit deeper into the logfile and found out that the "where" statement needs to be removed from the syntax as it seems to be already included in the internal synatx body. Just specifying "cc_east notnull and cc_east > 0" does the job.

That is different from 1.11 and 1.12, where the "where"-clause needs to be defined in the restriction sql itself.

Best regards
Klaus

#5 Updated by Juan Lucas Domínguez over 11 years ago

  • Status changed from Awaiting response to Fixed

Yes, I think it's better this way (without the word WHERE). Thanks for your interest.

#6 Updated by Joaquín del Cerro Murciano over 11 years ago

  • Target version changed from 2.0.0-final to 2.0.0-rc2

#7 Updated by Álvaro Anguix about 10 years ago

  • Status changed from Fixed to Closed

Also available in: Atom PDF