Ticket #1487 (closed defect: fixed)

Opened 16 months ago

Last modified 16 months ago

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: trunk
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

Changed 16 months ago by robe

  • status changed from new to closed
  • resolution set to fixed
  • component changed from postgis to documentation

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?

Note: See TracTickets for help on using tickets.