I also wish I had read that. I remember thinking it through, as I had kind of a hard time switching from Django ORM to SQLAlchemy, and ultimately I made the decision to use SQLAlchemy for everything because it minimized the possibility of me creating a schema that didn't perfectly match the ORM schema.
I worried that this would lead to having problems that weren't easily identifiable, and I was just learning Flask and SQLAlchemy at the time, I was making plenty of other mistakes on my own, and didn't need the added frustration.
Of course, as he says, it's a very fiddly process, and I either over or under-fiddled enough times to negate whatever frustration savings I might have otherwise avoided.
I worried that this would lead to having problems that weren't easily identifiable, and I was just learning Flask and SQLAlchemy at the time, I was making plenty of other mistakes on my own, and didn't need the added frustration.
Of course, as he says, it's a very fiddly process, and I either over or under-fiddled enough times to negate whatever frustration savings I might have otherwise avoided.