Opened 12 years ago
Closed 12 years ago
#1487 closed defect (fixed)
extensions not installing because AddRasterConstraints doc at odds with implementation
| Reported by: | robe | Owned by: | pramsey |
|---|---|---|---|
| Priority: | blocker | Milestone: | PostGIS 2.0.0 |
| Component: | documentation | Version: | master |
| Keywords: | Cc: |
Description
Seems the AddRasterConstraints has changed since it was documented.
Looks like all these were removed out of the end:
boolean num_bands=true, boolean pixel_types=true, boolean nodata_values=true, boolean extent=true
I'm going to assume this is an intentional change and just update the docs so extensions can install.
e.g used to be
boolean AddRasterConstraints(name rasttable, name rastcolumn, boolean srid, boolean scale_x, boolean scale_y, boolean blocksize_x, boolean blocksize_y, boolean same_alignment, boolean regular_blocking, boolean num_bands=true, boolean pixel_types=true, boolean nodata_values=true, boolean extent=true)
now its
boolean AddRasterConstraints(name rasttable, name rastcolumn, boolean srid, boolean scale_x, boolean scale_y, boolean blocksize_x, boolean blocksize_y, boolean same_alignment, boolean regular_blocking)
This is testing Paul's very soft launched alpha1 tar ball.
Change History (1)
comment:1 by , 12 years ago
| Component: | postgis → documentation |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
fixed at r8891. I was mistaken (the wrapper in pgAdmin cut my text). Nothing was taken away but out_db was added to AddRasterConstraints/DropRasterConstraints.
I am wondering about the utility of these functions since the variadic ones are so much easier to use. Who can keep 9+ boolean arguments straight in the head?