I wrote something like this for C# just yesterday as I couldn't find an sql builder with a real fluent interface. I found one which pretended to be fluent by re

I wrote something like this for C# just yesterday as I couldn't find an sql builder with a real fluent interface. I found one which pretended to be fluent by returning itself after each method call, but that completely misses the point, because you want each call to create a mutation but leave the original in tact. That allows me to build a query using all of the WHEREs and then branch it off into two separate queries.. one for COUNT and one to select the actual data. Just wondering.. did you create this to be used in the read layer of a DDD/CQS based system? Edit: actually looking at the source it appears this one is similar to the one i saw in C# where each call just returns the same builder rather than a new version