(Conditionally) Include resolved Datums & Scripts in responses.

[Cauterization]

In plutus-ledger DecoratedTxOut is the main type to which all logic is tied. Accordingly, most of the requests to kupo in our application are to receive a single DecoratedTxOut or Map from TxId's to DecoratedTxOut's.
We (and many other users I suppose) use kupo as a lightweight alternative to plutus-chain-index. However, while plutus-chain-index can retrieve a map of any size with a single request, it may require up to three requests to get one DecoratedTxOut with kupo (to get match, to get datum from its hash, and, in case of ScriptDecoratedTxOut - to get validator from script address). And this situation gets even worse when requesting many DecoratedTxOut's - this easily can take several hundred requests. We managed to get rid of this bottleneck in some parts of our application, but in some places this cannot be done without rewriting a huge part of cardano libraries
So maybe it would be possible to add a new endpoint that will do all these requests to database at once.

[KtorZ]

Hey, that's indeed something I've been discussing in the past with few people though so far but I have been missing a compelling use-case / argument for implement something like this.

it may require up to three requests

Indeed, but why is that a problem? Those requests are almost instant. Plus, Kupo already streams responses down to client row-by-row so in principle, you can even start querying inner schemas while receiving the response.

You do mention a "bottleneck" which suggests that this is somehow of a slow operation? (genuinely asking).

It shouldn't be too complicated to add a conditional flag on queries to automatically include datums & scripts, at the cost of some extra processing time.

[Cauterization]

I apologize for such a long absence. Our problem is that I did not experience these problems with performance, but some of our clients and programmers did. I tried to join the tables myself and compare whether there would be any changes and did not notice any significant difference. Apparently we will have to switch from decoratedTxOut's to kupo responses everywhere.
I apologize for bothering you needlessly. And thank you so much for such a cool project - we save a lot of time due to the fact that we don’t need to synchronize the plutus-chain-index.