Fix overzealous dooming in queryDatasets.

Unlike queryDataIds and queryDimensionRecords, one missing dataset type
here should not doom the entire query.

python/lsst/daf/butler/registries/sql.py

@@ -1038,7 +1038,7 @@ def queryDatasets(
                 check=check,
                 datasets=[parent_dataset_type],
             )
-            builder = self._makeQueryBuilder(summary, doomed_by=doomed_by)
+            builder = self._makeQueryBuilder(summary)
             # Add the dataset subquery to the query, telling the QueryBuilder
             # to include the rank of the selected collection in the results
             # only if we need to findFirst.  Note that if any of the

python/lsst/daf/butler/registry/tests/_registry.py

@@ -2666,6 +2666,16 @@ def testQueryResultSummaries(self):
         self.assertEqual(query5.count(exact=True), 0)
         messages = list(query5.explain_no_results())
         self.assertFalse(messages)
+        # This query should yield results from one dataset type but not the
+        # other, which is not registered.
+        query5 = registry.queryDatasets(["bias", "nonexistent"], collections=["biases"])
+        self.assertTrue(set(query5))
+        self.assertTrue(query5.any(execute=False, exact=False))
+        self.assertTrue(query5.any(execute=True, exact=False))
+        self.assertTrue(query5.any(execute=True, exact=True))
+        self.assertGreaterEqual(query5.count(exact=False), 1)
+        self.assertGreaterEqual(query5.count(exact=True), 1)
+        self.assertFalse(messages, list(query5.explain_no_results()))
 
     def testQueryDataIdsOrderBy(self):
         """Test order_by and limit on result returned by queryDataIds()."""