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
2012-11-28 17:18:41 -08:00
2012-11-07 14:19:48 -08:00
2013-02-20 10:43:32 -08:00
2011-10-31 17:22:06 +00:00
2011-10-31 17:22:06 +00:00
2012-09-16 19:33:43 -07:00
2012-12-16 08:58:28 -08:00
2012-12-17 11:26:59 -08:00
2012-12-17 11:26:59 -08:00
2011-10-31 17:22:06 +00:00
2013-01-03 17:13:56 -08:00
2013-01-03 17:13:56 -08:00
2012-11-28 17:18:41 -08:00
2013-01-03 17:13:56 -08:00
2013-01-14 18:40:22 -08:00