gvSIG bugs #872
Export to postgreSQL and MySQL doesn't work
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: |  Juan Lucas Domínguez | |||
| Category: | Database | |||
| Target version: | 2.0.0-devel-2050 | |||
| Severity: | Add-on version: | |||
| gvSIG version: | 2.0.0 | Add-on build: | ||
| gvSIG build: | 2049 | Add-on resolve version: | ||
| Operative System: | Linux | Add-on resolve build: | ||
| Keywords: | Proyecto: | |||
| Has patch: | No | Hito: | ||
| Add-on name: | Unknown |
Description
1. Run gvSIG
2. Open a new view.
3. Load a shapefile
4. Menu Layer>Export to
5. Select PostgreSQL format or MySQL format
6. Press next.
7. You get an error warning.
See attached the log file.
History
#1
Updated by Manuel Madrid almost 14 years ago
- File gvSIG_export_to_DB.log added
#2
Updated by Juan Lucas Domínguez almost 14 years ago
- Status changed from New to Fixed
Fixed dependency in config.xml and other small improvements.
Tested with PostgreSQL/PostGIS only and polygon layer only (but the initial error message does not happen even if the user intends to export to MySQL)
#3
Updated by María Maluenda over 13 years ago
- Status changed from Fixed to Closed
Closed in the gvSIG build 2051