gvSIG bugs #932

Impossible to choose DB connections in New Table dialog

Added by Antonio Falciano almost 12 years ago. Updated over 10 years ago.

Status:New% Done:

0%

Priority:High
Assignee:-
Category:-
Target version:-
Severity: Add-on name:Unknown
gvSIG version:1.12.0 Add-on version:
gvSIG build: Add-on build:
Operative System: Add-on resolve version:
Keywords:table, geodb Add-on resolve build:
Has patch:No

Description

It's not possible to choose any DB connections in the "Database" tab of "New table" dialog, even if there are active connections available in the "GeoDB Manager". Furthermore, without checking the source code, it seems like that "Database" tab is not implemented yet, because there are two columns asking to select a table and this is clearly redundant. Instead, I imagine that this tab should be implemented in the same way of spatial table ("Add layer" dialog, "GeoDB" tab), asking to choose a table on the left and its fields on the right and with table settings (e.g. SQL restrictions) at the bottom. Maybe, this one could be a feature request. Cheers.

new_postgis_table_choose_db.png (45.6 KB) Francisco Puga, 07/27/2012 04:54 PM

geodbmanager.png (24.6 KB) Antonio Falciano, 07/27/2012 05:12 PM

261
262

History

#1 Updated by Francisco Puga almost 12 years ago

  • Assignee set to Francisco Puga
  • Target version set to 1.12.0-final

#2 Updated by Antonio Falciano almost 12 years ago

  • Assignee deleted (Francisco Puga)
  • Target version deleted (1.12.0-final)
UPDATE: After the definition of a new "alphanumeric" DB connection from the "Database" tab of "New table" dialog , I was able to load a table from PostgreSQL. At this point, I think that it could be useful to be able:
  • to choose the fields from the table (by checkboxes or a full SQL query), more or less like in "Add layer" dialog, "GeoDB" tab;
  • to rename tables before loading them directly in a "Table settings" section (similar to "Layer settings" of "Add layer" dialog, "GeoDB" tab), in manner to don't have to rename them in the Project Manager (more time consuming) and because tables full name (e.g. localhost:5432/TABLENAME Table:"SCHEMANAME"."TABLENAME" could be quite illegible or meaningless for basic users, while it can be useful to have in the table properties, if the user want to understand where is the table source.

PS: please, convert this bug in a feature request, because I don't have the right to do it. Thanks.

#3 Updated by Francisco Puga almost 12 years ago

What is your OS? What build are you using?

In linux it seems good to me. See the attached screenshot.

Steps to reproduce:
1.- Open a View Document
2.- View > New Layer -> Postgis
3. Enter the name (this is just the name on the toc, don't worry about it), and the geometry type
4.- Enter the fields
5.- Choose an existent connection or create a new one. Then choose the schema in the combobox and type the tablename

#4 Updated by Antonio Falciano almost 12 years ago

Hi Francisco,
maybe there's a misunderstanding because I didn't explain well the issue. The choice of schema works fine to me too.
The issue I reported at the beginning is exclusively related to table documents. For instance, if I have just established a PostGIS connection in the GeoDB manager, I don't understand why this connection is not available in the "Database" tab of "New table" dialog, even if I want to load only an alphanumerical table.

I'm testing gvSIG 1.12 RC1 (build 1413) with JRE 1.6.0_21 on Windows Vista.

#5 Updated by Antonio Falciano almost 12 years ago

I have found the explanation: because the connection are made with two different drivers (see the attachment). In the screenshot it is shown that there two connections, instead of only one.

#6 Updated by Francisco Puga almost 12 years ago

  • Assignee deleted (Francisco Puga)
  • Target version deleted (1.12.0-final)

Hi,

You are right, geometric tables and alphanumeric tables are loaded using different drivers, and this behaviour is very deep in the gvSIG code. I agree with you on how it should be done, but this can not be accomplished in the short time, and less for this release.

I will keep the bug open, but i will remove the "target version"

#7 Updated by Álvaro Anguix over 10 years ago

  • Project changed from Application: gvSIG desktop to | gvSIG desktop 1

Also available in: Atom PDF