rethinkdb-dump fails if there are no tables

[AtnNn]

With a server that has no tables:

$ rethinkdb dump -c localhost:28018
NOTE: 'rethinkdb-dump' only dumps data and does *not* dump secondary indexes or
 cluster metadata.  You will need to recreate your secondary indexes and cluster
 setup yourself after you run 'rethinkdb-restore'.
Exporting to directory...
[========================================] 100% 
Failed to move temporary directory to output directory (/tmp/tmpEl4uw_/rethinkdb_dump_2014-01-24T13:47:13): No such file or directory
Error: rethinkdb-export failed

If I create a table, the dump succeeds.

This is possibly the same bug as http://stackoverflow.com/questions/21311887/how-can-i-run-rethinkdb-dump-export-in-rethinkdb-docker

Assigning to @Tryneus

[coffeemug]

We should also check export and such to make sure there are no other edge cases here (sorry for stating the obvious).

[Tryneus]

Dump uses export, this is actually an error happening in rethinkdb-export. Fix is pretty simple, will have it up soon.

[Tryneus]

Fix is up in review 1154.

[Tryneus]

The fix has been approved and merged into next in commit fb4e9df, and cherry-picked into v1.11.x in commit 79dd40c. Will be in release 1.11.4 and/or 1.12.

[AtnNn]

I have released a new version of the Python driver with this change (version 1.11.0-2), it should be available on pypi shortly.