db object implements a protocol that supplies (the implementation of)
d/q. What we have in our app is a wrapper that intercepts some of those protocol functions and (possibly) amends/replaces their implementation. For one, we have a wrapper for
d/q logging queries and their results to a tap.
By locally do you mean
dev-local? I think in that case calling
d/delete-database does indeed destroy the data on disk. I use this during development to re-seed my local db while testing out schema changes. I have it on a hotkey.