gvSIG bugs #2100
direct-sql sources select-sql creation problem
Status: | Closed | % Done: | 0% | |
---|---|---|---|---|
Priority: | Normal | Spent time: | - | |
Assignee: | Juan Lucas Domínguez | |||
Category: | Database | |||
Target version: | 2.1.0-2217-devel | |||
Severity: | Add-on version: | |||
gvSIG version: | 2.0.0 | Add-on build: | ||
gvSIG build: | 2066 | Add-on resolve version: | ||
Operative System: | Add-on resolve build: | |||
Keywords: | Proyecto: | |||
Has patch: | Yes | Hito: | ||
Add-on name: | Unknown |
Description
Here is a patch which solves problems form when you try to create layer from a custom SQL.
In Postgis, custom SQL must return a column as geometry, but, as Postgis-Dal provider use WKB to read it, the final sql must use asBinary
function to get geometry data. Now, DAL uses the specified SQL directly (without convert geometry).
The patch changes this behaviour creating the select-SQL as a standard source but using the required query as subquery (on FROM clause).
Related issues
History
#1 Updated by Juan Lucas Domínguez over 10 years ago
- Assignee set to Juan Lucas Domínguez
#2 Updated by Juan Lucas Domínguez over 10 years ago
- Status changed from New to Fixed
- Target version set to 2.1.0-2223-rc1
Fixed SQL composition for custom SQL. Patch provided by jmvivo.
#3 Updated by Joaquín del Cerro Murciano over 10 years ago
- Target version changed from 2.1.0-2223-rc1 to 2.1.0-2217-devel
#4 Updated by Álvaro Anguix over 10 years ago
- Status changed from Fixed to Closed