Good advice. One needs to be careful with any tight-coupling, and not just because of testing concerns. Of course, there's the pragmatic side to this as well... over engineering for a small "throw away" application just to adhere to enterprise "best practices"
can be a waste of time. If this were a mission critical and/or large application, I'd recommend the repository pattern here.
Yeah, for this project there's really no point to force loose coupling on the model side of things, as changing our system from Oracle to something else would be a nightmare (thanks to all of the existing tightly coupled apps )