PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` # Generated by default/object.tt package Paws::DynamoDB::AttributeValueUpdate; use Moose; has Action => (is => 'ro', isa => 'Str'); has Value => (is => 'ro', isa => 'Paws::DynamoDB::AttributeValue'); 1; ### main pod documentation begin ### =head1 NAME Paws::DynamoDB::AttributeValueUpdate =head1 USAGE This class represents one of two things: =head3 Arguments in a call to a service Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. Each attribute should be used as a named argument in the calls that expect this type of object. As an example, if Att1 is expected to be a Paws::DynamoDB::AttributeValueUpdate object: $service_obj->Method(Att1 => { Action => $value, ..., Value => $value }); =head3 Results returned from an API call Use accessors for each attribute. If Att1 is expected to be an Paws::DynamoDB::AttributeValueUpdate object: $result = $service_obj->Method(...); $result->Att1->Action =head1 DESCRIPTION For the C operation, represents the attributes to be modified, the action to perform on each, and the new value for each. You cannot use C to update any primary key attributes. Instead, you will need to delete the item, and then use C to create a new item with new attributes. Attribute values cannot be null; string and binary type attributes must have lengths greater than zero; and set type attributes must not be empty. Requests with empty values will be rejected with a C exception. =head1 ATTRIBUTES =head2 Action => Str Specifies how to perform the update. Valid values are C (default), C, and C. The behavior depends on whether the specified primary key already exists in the table. B is found in the table:> =over =item * C - Adds the specified attribute to the item. If the attribute already exists, it is replaced by the new value. =item * C - If no value is specified, the attribute and its value are removed from the item. The data type of the specified value must match the existing value's data type. If a I of values is specified, then those values are subtracted from the old set. For example, if the attribute value was the set C<[a,b,c]> and the C action specified C<[a,c]>, then the final attribute value would be C<[b]>. Specifying an empty set is an error. =item * C - If the attribute does not already exist, then the attribute and its values are added to the item. If the attribute does exist, then the behavior of C depends on the data type of the attribute: =over =item * If the existing attribute is a number, and if C is also a number, then the C is mathematically added to the existing attribute. If C is a negative number, then it is subtracted from the existing attribute. If you use C to increment or decrement a number value for an item that doesn't exist before the update, DynamoDB uses 0 as the initial value. In addition, if you use C to update an existing item, and intend to increment or decrement an attribute value which does not yet exist, DynamoDB uses C<0> as the initial value. For example, suppose that the item you want to update does not yet have an attribute named I, but you decide to C the number C<3> to this attribute anyway, even though it currently does not exist. DynamoDB will create the I attribute, set its initial value to C<0>, and finally add C<3> to it. The result will be a new I attribute in the item, with a value of C<3>. =item * If the existing data type is a set, and if the C is also a set, then the C is added to the existing set. (This is a I operation, not mathematical addition.) For example, if the attribute value was the set C<[1,2]>, and the C action specified C<[3]>, then the final attribute value would be C<[1,2,3]>. An error occurs if an Add action is specified for a set attribute and the attribute type specified does not match the existing set type. Both sets must have the same primitive data type. For example, if the existing data type is a set of strings, the C must also be a set of strings. The same holds true for number sets and binary sets. =back This action is only valid for an existing attribute whose data type is number or is a set. Do not use C for any other data types. =back B is found:> =over =item * C - DynamoDB creates a new item with the specified primary key, and then adds the attribute. =item * C - Nothing happens; there is no attribute to delete. =item * C - DynamoDB creates an item with the supplied primary key and number (or set of numbers) for the attribute value. The only data types allowed are number and number set; no other data types can be specified. =back =head2 Value => L Represents the data for an attribute. Each attribute value is described as a name-value pair. The name is the data type, and the value is the data itself. For more information, see Data Types (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html#HowItWorks.DataTypes) in the I. =head1 SEE ALSO This class forms part of L, describing an object used in L =head1 BUGS and CONTRIBUTIONS The source code is located here: L Please report bugs to: L =cut