Merge branch 'blobs'

Author: kriszyp

docs/developers/applications/defining-schemas.md

@@ -191,17 +191,17 @@ If you do not define a schema for a table and create a table through the operati
 
 HarperDB supports the following field types in addition to user defined (object) types:
 
-* `String`: String/text.
-* `Int`: A 32-bit signed integer (from -2147483648 to 2147483647).
-* `Long`: A 54-bit signed integer (from -9007199254740992 to 9007199254740992).
-* `Float`: Any number (any number that can be represented as a [64-bit double precision floating point number](https://en.wikipedia.org/wiki/Double-precision\_floating-point\_format). Note that all numbers are stored in the most compact representation available).
-* `BigInt`: Any integer (negative or positive) with less than 300 digits. (Note that `BigInt` is a distinct and separate type from standard numbers in JavaScript, so custom code should handle this type appropriately.)
-* `Boolean`: true or false.
-* `ID`: A string (but indicates it is not intended to be human readable).
-* `Any`: Any primitive, object, or array is allowed.
-* `Date`: A Date object.
-* `Bytes`: Binary data (as a Buffer or Uint8Array).
-* `Blob`: Binary data designed for large blocks of data that can be streamed. It is recommend that you use this for binary data that will typically be larger than 20KB.
+* `String`: String/text
+* `Int`: A 32-bit signed integer (from -2147483648 to 2147483647)
+* `Long`: A 54-bit signed integer (from -9007199254740992 to 9007199254740992)
+* `Float`: Any number (any number that can be represented as a [64-bit double precision floating point number](https://en.wikipedia.org/wiki/Double-precision\_floating-point\_format). Note that all numbers are stored in the most compact representation available)
+* `BigInt`: Any integer (negative or positive) with less than 300 digits (Note that `BigInt` is a distinct and separate type from standard numbers in JavaScript, so custom code should handle this type appropriately)
+* `Boolean`: true or false
+* `ID`: A string (but indicates it is not intended to be human readable)
+* `Any`: Any primitive, object, or array is allowed
+* `Date`: A Date object
+* `Bytes`: Binary data as a Buffer or Uint8Array
+* `Blob`: Binary data as a [Blob](../../technical-details/reference/blob.md), designed for large blocks of data that can be streamed. It is recommend that you use this for binary data that will typically be larger than 20KB.
 
 #### Renaming Tables
 

docs/technical-details/reference/data-types.md

@@ -41,7 +41,13 @@ Dates can be stored as a specific data type. This is not supported in JSON, but
 
 ## Binary Data
 
-Binary data can be stored in property values as well. JSON doesn’t have any support for encoding binary data, but MessagePack and CBOR support binary data in data structures, and this will be preserved in HarperDB. Custom Functions can also store binary data by using NodeJS’s Buffer or Uint8Array instances to hold the binary data. The GraphQL schema type name is `Bytes`.
+Binary data can be stored in property values as well, with two different data types that are available:
+
+### Bytes
+JSON doesn’t have any support for encoding binary data, but MessagePack and CBOR support binary data in data structures, and this will be preserved in HarperDB. Custom Functions can also store binary data by using NodeJS’s Buffer or Uint8Array instances to hold the binary data. The GraphQL schema type name is `Bytes`.
+
+### Blobs
+Binary data can also be stored with [`Blob`s](blob.md), which can scale much better for larger content than `Bytes`, as it is designed to be streamed and does not need to be held entirely in memory. It is recommended that `Blob`s are used for content larger than 20KB. 
 
 ## Explicit Map/Set