Sorry, I typoed up there - I did in fact mean to talk about q.fetch_only(), as that’s how you can replicate the behaviour of “only fetch these columns, but load others on demand if they’re accessed”. This should solve @ianbuywise’s problem.
@divyeshlakhotia - just checking, have you tested your app with Accelerated Tables and determined that this specifically is a problem, or is this speculative for now?