diff --git a/include/caosdb/transaction.h b/include/caosdb/transaction.h
index c246bc5905f6f79cd16c2ded29f03ff0d3d52e18..17130505ef5c9ac864331f9e03b6dd58980b3ffc 100644
--- a/include/caosdb/transaction.h
+++ b/include/caosdb/transaction.h
@@ -246,17 +246,6 @@ private:
   std::unique_ptr<Entity> entity;
 };
 
-// TODO(fspreck) One possibility for count-queries: Transaction gets a
-// GetQueryCount function that returns exactly this. In case of a
-// single FIND Query this will be equivalent to the Size of the
-// ResultSet, but it may be different in case of Query + RetrieveById,
-// and in case of COUNT queries which have an empty ResultSet. We have
-// to think about how to extend this to transactions with more than
-// one query in the future. My suggestion is to treat a transaction
-// with more than one query as the union of the query results in which
-// case the query count would return the cumulative number of
-// results. This would even allow the combination of FIND, FIND
-// unique, and COUNT, albeit a little strangely.
 /**
  * @brief Create a transaction via `CaosDBConnection.createTransaction()`
  */