In __wt_btcur_search_near(), there's a return of "exact" that always gets set to 0, indicating an exact match.
This needs to be hooked up to the row-store search function so we can return the result of the last search. Michael: do we want to always return the record that's one-entry smaller than the entry the application searched for, unless it's the first record in the tree?
What should the settings be for column-store searches? There's not really a less-than or greater-than notion, you either found the record or it doesn't exist.