[PATCH 20/21] search: query_xover uses skeleton DB iff available

["Eric Wong (Contractor, The Linux Foundation)" <e@80x24.org>]

The skeleton DB is where we store all the information needed
for NNTP overviews via XOVER.  This seems to be the only change
necessary (besides eventually handling duplicates) necessary
to support our nntpd interface for v2 repositories.
---
 lib/PublicInbox/Search.pm | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/lib/PublicInbox/Search.pm b/lib/PublicInbox/Search.pm
index 6b14942..a796cf6 100644
--- a/lib/PublicInbox/Search.pm
+++ b/lib/PublicInbox/Search.pm
@@ -317,11 +317,17 @@ sub num_range_processor {
 sub query_xover {
 	my ($self, $beg, $end, $offset) = @_;
 	my $qp = Search::Xapian::QueryParser->new;
-	$qp->set_database($self->{xdb});
+	$qp->set_database($self->{skel} || $self->{xdb});
 	$qp->add_valuerangeprocessor($self->num_range_processor);
 	my $query = $qp->parse_query("$beg..$end", QP_FLAGS);
 
-	_do_enquire($self, $query, {num => 1, limit => 200, offset => $offset});
+	my $opts = {
+		enquire => enquire_skel($self),
+		num => 1,
+		limit => 200,
+		offset => $offset,
+	};
+	_do_enquire($self, $query, $opts);
 }
 
 sub lookup_skeleton {
-- 
EW