Fix issue with change in copy "floating" datatype
authorJeff Godin <jgodin@tadl.org>
Thu, 13 Feb 2014 20:26:25 +0000 (15:26 -0500)
committerGalen Charlton <gmc@esilibrary.com>
Thu, 13 Feb 2014 20:35:43 +0000 (15:35 -0500)
commitb0d7224f590b5b28e44e02eb05272a1e26373948
tree92b6953363f6565014555953efb3a59a5b274d89
parentc6594b6682c66e0621713e0df9007521b499550c
Fix issue with change in copy "floating" datatype

In recent versions of Evergreen, asset.copy.floating changed from a bool
to an int, which results in an error like the following:

 operator does not exist: integer = boolean
 SELECT CASE floating WHEN TRUE THEN 'Y' ELSE NULL END FROM a...

This change attempts to accommodate this change in datatype in a
backward-compatible way.

Signed-off-by: Jeff Godin <jgodin@tadl.org>
Signed-off-by: Galen Charlton <gmc@esilibrary.com>
collectionHQ/functions.sql