bowlesj wrote:
I have a lot of queries I was going to handle this way and of course the strings are much bigger.
I would recommend organizing these into Model classes to promote reuse and make maintenance easier down the road. Inject you connection class into these for reuse/maintenance as well. If your queries are all variations of simple queries, you can look into the several good ActiveRecord and ORM implementations in PHP.
FYI - Ultimately for performance, everyone does the same thing -- that is push the rendered HTML output of the app to a cache closer to the user so they are served static pages (that are updated at intervals or when the data changes). Take a look at the libraries from projects like Symfony that are used by many other projects. I would recommend only reinventing the wheels unique to your application.