Open GoogleCodeExporter opened 9 years ago
IMHO, it should be left as is by default, with a --replace option added that
does an optional 'get', check and 'delete' if required.
Googlecl is primarily useful for further scripting, rather than literally
typing the commands on the cli. Doing a replace using the gdata-python library
requires a 'get' to find existing photo, a 'delete' to delete it if it exists,
and finally a 'post' to put up the new version. And doing a 'get' per-photo to
check whether to for a replace by default is inefficient, especially when many
scripts will be batch processing.
In my own batch upload scripts, I do a 'get' on the album to retrieve the
photo's that are currently there, then check (and remove) against those I'm
uploading. This is far more efficient than doing a 'get' on each photo.
Original comment by moro...@gmail.com
on 1 Apr 2012 at 12:45
Original issue reported on code.google.com by
brunolu...@gmail.com
on 20 Nov 2011 at 8:58