Opened 15 years ago
Closed 15 years ago
#816 closed defect (fixed)
ODBC column editor not correctly persisting key/geometry information
| Reported by: | jng | Owned by: | ksgeograf |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Maestro | Version: | |
| Severity: | critical | Keywords: | |
| Cc: | External ID: |
Description
When you configure a ODBC table to be a feature class, the following happens:
- The key field for a table (if specified) is not written to the configuration xml (the configuration xml should have (xs:element -> xs:key) elements for keys I specified)
- If a z-component is specified for the geometry, it gets replaced with the y-component.
- If you reload the column editor with the updated configuration document, it does not correctly load the X/Y/Z column information.
Attachments (1)
Change History (3)
by , 15 years ago
| Attachment: | geometry_fix.patch added |
|---|
comment:1 by , 15 years ago
| Status: | new → assigned |
|---|---|
| Version: | 2.0.1 |
I applied the patch in r3619. I can see the problem with the missing primary key. Thanks for reporting it, and thanks for the patch.
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
I found the problem. It was possible to re-assign the primary key on a table, but if the table had no primary keys defined, it was not possible to assign a primary key.
Fixed in r3729.
Note:
See TracTickets
for help on using tickets.
Proposed patch to fix points 2. and 3.