Opened 12 years ago
Closed 12 years ago
#2141 closed enhancement (fixed)
[raster] Report _add_raster_constraint violation error details
Reported by: | mloskot | Owned by: | dustymugs |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.0.3 |
Component: | raster | Version: | 2.0.x |
Keywords: | history | Cc: |
Description
Currently, _add_raster_constraint functiond does not report any details about the reason of skipped constraint. It makes it difficult to diagnose constraint problems.
For example, without replacing the blocksize constraint conditions (see patch for #2122), the blocksize constraint is silently skipped with no detailed reason provided.
Attachments (1)
Change History (3)
by , 12 years ago
Attachment: | _add_raster_constraint_violation_details.patch added |
---|
comment:1 by , 12 years ago
Status: | new → assigned |
---|
comment:2 by , 12 years ago
Keywords: | history added |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Type: | defect → enhancement |
Version: | trunk → 2.0.x |
Note:
See TracTickets
for help on using tickets.
Add SQLSTATE details to raised notice. — Alternatively, add WHEN SQLSTATE '23514' THEN to explicitly report check_violation.