Opened 4 months ago

Closed 4 months ago

Last modified 4 months ago

#5191 closed defect (fixed)

Use integer instead of int4

Reported by: robe Owned by: robe
Priority: medium Milestone: PostGIS 2.5.8
Component: postgis Version: 2.5.x
Keywords: Cc:

Description

integer is the canonical preferred way of specifying int4 in postgresql functions. In fact if you define a function as input int4 or output int4, PostgreSQL changes it to integer when you script the function.

To make it easier for our Perl script to determine a function is installed, we should standardize on integer instead of int4

Change History (5)

comment:1 by Regina Obe <lr@…>, 4 months ago

In 97de448/git:

Use integer instead of int4. References #5191 for PostGIS 3.3.0

comment:2 by Regina Obe <lr@…>, 4 months ago

In 7ce341c/git:

Use integer instead of int4. References #5191 for PostGIS 3.3.0. For raster, geography, and legacy

comment:3 by Regina Obe <lr@…>, 4 months ago

In 37d8bb47/git:

Use the more standard integer instead of int4. References #5191 for PostGIS 3.2.3

comment:4 by pramsey, 4 months ago

Resolution: fixed
Status: assignedclosed

comment:5 by Regina Obe <lr@…>, 4 months ago

In caf4a02/git:

Use the more standard integer instead of int4. References #5191 for PostGIS 3.1.7

Note: See TracTickets for help on using tickets.