/usr/lib/python2.6/site-packages/boto/dynamodb2
Edit: /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyc (14472B)
Ñò
Å-õSc @ sP d d k l Z d d k l Z d e f d „ ƒ YZ d e f d „ ƒ YZ d S( iÿÿÿÿ( t deepcopy( t Dynamizert NEWVALUEc B s e Z RS( ( t __name__t
__module__( ( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyR s t Itemc B s e Z d Z d e d „ Z d „ Z d „ Z d „ Z d „ Z d „ Z
d „ Z d d „ Z d „ Z
d
„ Z d „ Z e Z d „ Z d d
„ Z d „ Z d „ Z d „ Z d „ Z d „ Z d d „ Z d „ Z d „ Z d „ Z d „ Z e d „ Z d „ Z RS( s
An object representing the item data within a DynamoDB table.
An item is largely schema-free, meaning it can contain any data. The only
limitation is that it must have data for the fields in the ``Table``'s
schema.
This object presents a dictionary-like interface for accessing/storing
data. It also tries to intelligently track how data has changed throughout
the life of the instance, to be as efficient as possible about updates.
Empty items, or items that have no data, are considered falsey.
c C sq | | _ | | _ h | _ | | _ t ƒ | _ | i d j o
h | _ n | i o t | i ƒ | _ n d S( sÃ
Constructs an (unsaved) ``Item`` instance.
To persist the data in DynamoDB, you'll need to call the ``Item.save``
(or ``Item.partial_save``) on the instance.
Requires a ``table`` parameter, which should be a ``Table`` instance.
This is required, as DynamoDB's API is focus around all operations
being table-level. It's also for persisting schema around many objects.
Optionally accepts a ``data`` parameter, which should be a dictionary
of the fields & values of the item.
Optionally accepts a ``loaded`` parameter, which should be a boolean.
``True`` if it was preexisting data loaded from DynamoDB, ``False`` if
it's new data from the user. Default is ``False``.
Example::
>>> users = Table('users')
>>> user = Item(users, data={
... 'username': 'johndoe',
... 'first_name': 'John',
... 'date_joined': 1248o61592,
... })
# Change existing data.
>>> user['first_name'] = 'Johann'
# Add more data.
>>> user['last_name'] = 'Doe'
# Delete data.
>>> del user['date_joined']
# Iterate over all the data.
>>> for field, val in user.items():
... print "%s: %s" % (field, val)
username: johndoe
first_name: John
date_joined: 1248o61592
N( t tablet _loadedt
_orig_datat _dataR t
_dynamizert NoneR ( t selfR t datat loaded( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyt __init__ s *
c C s | i i | d ƒ S( N( R t getR ( R t key( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyt __getitem__P s c C s | | i |
>> user.needs_save()
False
>>> user['first_name'] = 'Johann'
>>> user.needs_save()
True
R R R N( R R) t Falset lent True( R R
t
needs_savet kind( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyR- ˜ s
c C s t | i ƒ | _ d S( sM
Marks an ``Item`` instance as no longer needing to be saved.
Example:
>>> user.needs_save()
False
>>> user['first_name'] = 'Johann'
>>> user.needs_save()
True
>>> user.mark_clean()
>>> user.needs_save()
False
N( R R R ( R ( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyt
mark_cleanµ s c C s d S( sß
DEPRECATED: Marks an ``Item`` instance as needing to be saved.
This method is no longer necessary, as the state tracking on ``Item``
has been improved to automatically detect proper state.
N( ( R ( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyt
mark_dirtyÇ s c C sg h | _ x< | i d h ƒ i ƒ D]" \ } } | i i | ƒ | | >> user['last_name'] = 'Doh!'
# Only the last name field will be sent to DynamoDB.
>>> user.partial_save()
R@ RA (
R8 RK R* R t removet KeyErrorRD R t _update_itemR/ ( R R RE R@ t fieldnameR RA t returned( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyt partial_savep s
c C sp | i ƒ o
| o t S| i ƒ } d } | t j o | i ƒ } n | i i | d | ƒ} | i ƒ | S( sU
Saves all data to DynamoDB.
By default, this attempts to ensure that none of the underlying
data has changed. If any fields have changed in between when the
``Item`` was constructed & when it is saved, this call will fail so
as not to cause any data loss.
If you're sure possibly overwriting data is acceptable, you can pass
an ``overwrite=True``. If that's not acceptable, you may be able to use
``Item.partial_save`` to only write the changed field data.
Optionally accepts an ``overwrite`` parameter, which should be a
boolean. If you provide ``True``, the item will be forcibly overwritten
within DynamoDB, even if another process changed the data in the
meantime. (Default: ``False``)
Returns ``True`` on success, ``False`` if no save was performed.
Example::
>>> user['last_name'] = 'Doh!'
# All data on the Item is sent to DynamoDB.
>>> user.save()
# If it fails, you can overwrite.
>>> user.save(overwrite=True)
RA N( R- R* RF R RD R t _put_itemR/ ( R t overwriteRE RA RP ( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyt savež s
c C s | i ƒ } | i i | S( sª
Deletes the item's data to DynamoDB.
Returns ``True`` on success.
Example::
# Buh-bye now.
>>> user.delete()
( R8 R t delete_item( R R7 ( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyt deleteË s N( R R t __doc__R R* R R R R R R R R R R R t __nonzero__R) R- R/ R0 R4 R8 R; RD R# RF RK RQ RT RV ( ( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyR s6 6 $
4 $ . -N( t copyR t boto.dynamodb2.typesR t objectR R ( ( ( s8 /usr/lib/python2.6/site-packages/boto/dynamodb2/items.pyt s