The good news is, you can always fall back to writing Ecto queries directly, as Ash resources are built on top of Ecto schemas. I tend to do this if I need to write data migrations - using resource actions there isn’t great because then the migrations need to be kept up to date (otherwise your app won’t compile).
I’ll have a think about this one, see if we can make a mention about it somewhere. Thanks for the feedback!