I'm currently starting a project from scratch using the Zend Framework. I'm experienced in PHP and SQL, but I've never used a PHP framework before.
Regarding the database side of things - a lot of the tutorials use the Zend classes to wrap the SQL so that you don't have to write raw SQL. For example:
$select = $this->select()
->from('MyTable')
->order('MyField');
However, my preference is writing SQL as this is what I'm used to and feel that for both flexibility and speed to development, this is the best decision. (Note that I actually mean parameterised SQL using PDO, not completely raw SQL).
My questions are:
Are there any issues with doing it this way? Am I better in the long run going with the Zend way of doing database queries? Is it common for Zend developers to write the SQL themselves rather than using the Zend-style method queries?
What's the most common way of implementing this whilst keeping with an MVC code layout? A Google gave me this link (and similar), but that has the SQL in the controller (which I don't want). I still want to create my own application specific model classes, and adhere to the MVC split. I can think of plenty of places to instantiate the Zend_Db_Adapter_Pdo_Mysql class for using in my models - however I'd like to know what the most common design pattern is for this.