[postgis-tickets] [PostGIS] #3832: No support for bigint in shp2pgsql.

[PostGIS]

#3832: No support for bigint in shp2pgsql.
--------------------------+---------------------------
  Reporter:  EvanCarroll  |      Owner:  pramsey
      Type:  defect       |     Status:  closed
  Priority:  low          |  Milestone:  PostGIS 2.4.0
 Component:  postgis      |    Version:  2.3.x
Resolution:  fixed        |   Keywords:
--------------------------+---------------------------
Changes (by pramsey):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Interested to know if r15639 makes a meaningful difference. The actual
 stack question seemed to not make sense: the behaviour in an over-wide
 integer field in shp2pgsql is to use numeric as the type, not double, so
 the fact that the use was seeing double types is not consistent with what
 the code says. If their data was in a field with a non-zero precision
 value, it might end up treated as float no matter what.

 The important thing to note is that ogr and shp2pgsql both guess the type
 mappings based on the dbf header, not the data in the file, so if your
 header says a field is a number(12,5), you're getting a float field there,
 even if the data itself is just small integers.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3832#comment:1>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.