ti.getanalysisunitbyid fix applied. Returns double precision.

SimonGoring · SimonGoring · commit 1470395014de · 2020-10-29T09:14:34.000-07:00
Issue #8 indicated that depth and thickness were being returned as integers. This was a result of the typecast to `numeric` apparently. Keeping the type as a double precision (float).
diff --git a/function/ti/getanalysisunitbyid.sql b/function/ti/getanalysisunitbyid.sql
@@ -1,11 +1,14 @@
 CREATE OR REPLACE FUNCTION ti.getanalysisunitbyid(_analunitid integer)
-RETURNS TABLE(collectionunitid integer, analysisunitname character varying, depth numeric, thickness numeric)
+RETURNS TABLE(collectionunitid integer,
+              analysisunitname character varying,
+              depth double precision,
+              thickness double precision)
 LANGUAGE sql
 AS $function$
   SELECT au.collectionunitid,
          au.analysisunitname,
-         au.depth::numeric,
-         au.thickness::numeric
+         au.depth,
+         au.thickness
   FROM ndb.analysisunits AS au
   WHERE analysisunitid = _analunitid;
 $function$
