amayank b2c50f1c3f Fix for the weird behaviour encountered by ldb Get where it could read only the second-latest value
Summary:
Changed the Get and Scan options with openForReadOnly mode to have access to the memtable.
Changed the visibility of NewInternalIterator in db_impl from private to protected so that
the derived class db_impl_read_only can call that in its NewIterator function for the
scan case. The previous approach which changed the default for flush_on_destroy_ from false to true
caused many problems in the unit tests due to empty sst files that it created. All
unit tests pass now.

Test Plan: make clean; make all check; ldb put and get and scans

Reviewers: dhruba, heyongqiang, sheki

Reviewed By: dhruba

CC: kosievdmerwe, zshao, dilipj, kailiu

Differential Revision: https://reviews.facebook.net/D8697
2013-02-20 10:45:52 -08:00
..
2011-10-31 17:22:06 +00:00
2011-10-31 17:22:06 +00:00
2012-11-28 17:18:41 -08:00
2012-12-07 10:48:46 -08:00
2013-01-31 15:20:24 -08:00
2012-08-28 11:43:33 -07:00
2011-10-31 17:22:06 +00:00
2013-01-31 15:20:24 -08:00
2013-01-31 15:20:24 -08:00
2012-04-17 08:36:46 -07:00
2011-10-31 17:22:06 +00:00
2011-10-31 17:22:06 +00:00
2013-02-04 19:42:40 -08:00
2011-10-31 17:22:06 +00:00
2011-10-31 17:22:06 +00:00
2011-10-31 17:22:06 +00:00