We've seen some cases of people trying to use db.collection.remote() instead of .drop() so that they won't lose indexes and sharding/chunk information. Would it make sense to support something equivalent to SQL TRUNCATE TABLE command which dumps the data from a collection (and indexes) but does not remove index definitions or sharding meta-data?