@@ -212,16 +212,17 @@ each field. Every field on the object must be included here; if you miss
212212any they'll be completely bypassed during DynamoDB's initialization and
213213will not appear on the model objects.
214214
215- By default, fields are assumed to be of type ` :string ` . Other built-in
216- types are ` :integer ` , ` :number ` , ` :set ` , ` :array ` , ` :map ` , ` :datetime ` ,
217- ` date ` , ` :boolean ` , ` :raw ` and ` :serialized ` . ` array ` and ` map ` match
218- List and Map DynamoDB types respectively. ` raw ` type means you can store
219- Ruby Array, Hash, String and numbers. If built-in types do not suit you,
220- you can use a custom field type represented by an arbitrary class,
221- provided that the class supports a compatible serialization interface.
222- The primary use case for using a custom field type is to represent your
223- business logic with high-level types, while ensuring portability or
224- backward-compatibility of the serialized representation.
215+ By default, fields are assumed to be of type ` string ` . Other built-in
216+ types are ` integer ` , ` number ` , ` set ` , ` array ` , ` map ` , ` datetime ` ,
217+ ` date ` , ` boolean ` , ` binary ` , ` raw ` and ` serialized ` . ` array ` and
218+ ` map ` match List and Map DynamoDB types respectively. ` raw ` type means
219+ you can store Ruby Array, Hash, String and numbers. If built-in types do
220+ not suit you, you can use a custom field type represented by an
221+ arbitrary class, provided that the class supports a compatible
222+ serialization interface. The primary use case for using a custom field
223+ type is to represent your business logic with high-level types, while
224+ ensuring portability or backward-compatibility of the serialized
225+ representation.
225226
226227#### Note on boolean type
227228
0 commit comments