Use double precision as numeric type

As shown in the tests, that type has the flexibility of being able to be cast to from any other numeric type. This gives us flexibility without bloating the API with lots of type-specific functions.
2017-07-07 13:08:41 +02:00
parent e123079e92
commit 074234b8da
2 changed files with 6 additions and 6 deletions
@@ -42,7 +42,7 @@
 - name: cdb_geocode_postalcode_polygon
  return_type: Geometry
  params:
-    - { name: postal_code,  type: integer}
+    - { name: postal_code,  type: double precision}
    - { name: country_name, type: text}

 - name: cdb_geocode_postalcode_point
@@ -54,7 +54,7 @@
 - name: cdb_geocode_postalcode_point
  return_type: Geometry
  params:
-    - { name: postal_code,  type: integer}
+    - { name: postal_code,  type: double precision}
    - { name: country_name, type: text}

 - name: cdb_geocode_ipaddress_point