Uint8Array data (e.g. Postgres "bytea" type) erroneously considered "…

…undefined" by recent 0.11.7 update. (#1601)

* Made modification so that attributes with data stored in typed arrays such as Uint8Arrays are treated as "Arrays" vs as "Objects". For example, pgsql "bytea" type column data is passed back as Uint8Arrays by the node pgsql driver "pg" and without this modification, such data will fail the "containsUndefined" test.

* Made modification so that attributes with data stored in typed arrays such as Uint8Arrays are automatically treated as "not undefined" (vs as "Array" which will result in unecessary testing of Array contents). For example, pgsql "bytea" type column data is passed back as Uint8Arrays by the node pgsql driver "pg" and without this modification, such data will fail the "containsUndefined" test with previous implementation.

src/helpers.js

@@ -1,6 +1,6 @@
 /* eslint no-console:0 */
 
-import { map, pick, keys, isFunction, isUndefined, isObject, isArray } from 'lodash'
+import { map, pick, keys, isFunction, isUndefined, isObject, isArray, isTypedArray } from 'lodash'
 import chalk from 'chalk';
 
 // Pick off the attributes from only the current layer of the object.
@@ -47,6 +47,9 @@ export function exit(msg) {
 export function containsUndefined(mixed) {
   let argContainsUndefined = false;
 
+  if (isTypedArray(mixed))
+    return false;
+
   if(mixed && isFunction(mixed.toSQL)) {
     //Any QueryBuilder or Raw will automatically be validated during compile.
     return argContainsUndefined;