Repository navigation
Determine if there is a better way to perform datastore.connection.Connection.delete_entity with the API #169
Description
From TODO:
# TODO: Is this the right way to handle deleting
# (single and multiple as separate methods)?See datastore.connection.Connection.delete_entity for relevant code and #146 for some context.
git blame output
dec0e7c6 (JJ Geewax 2014-01-28 15:15:40 -0500 387) # TODO: Is this the right way to handle deleting
Activity
tseaver commentedon Oct 17, 2014
I think we could safely drop 'delete_entity' from the Connection API: the 'Entity.delete' implementation could just as well delegate to 'Connection.delete_entities'.
Merge pull request #257 from tseaver/168_169-connection_delete_entities
Fix for googleapis#169
chore(main): release 1.7.0 (#169)
chore(main): release 1.10.1 (#169)
70 remaining items
chore: add library type to .repo-metadata.json (#169)
chore: fix prerelease_deps nox session [autoapprove] (#169)
fix: Change `ocr_line` `<span>` to include all `ocr_word` (#169)
chore(main): release 0.10.2-alpha (#174)
fix: `docai_utilities.py` to return `Optional` (#176)
chore(python): group renovate prs (#169)
fix: name parameter to indicate snapshot support (#169)
Some additional tests for Model.__eq__() (#169)
chore(deps): update all dependencies (#169)
fix: allow space in checksum header (#170)
django: store DurationField as INT64 rather than STRING
feat: remove adding a dummy WHERE clause into UPDATE and DELETE state…
chore: release 2.1.0 (#173)
chore: fix repo-metadata as required (#169)
chore(deps): update all dependencies (#169)