Re: [fw-db] The best way to approach the database

And what do you say about using views on database for joins. That's what I'm doing. I have a default database view for each model, and an extended instance of an abstraction of Zend_Db_Table, where I can set if I want to perform the select from a view, straight from the table or if I want to select from any other relation instead. I'd like to have an opinion from you according to performance, design patterns and any other convention you know.
Thanks,

/**
 * Ramses Paiva
 * Software Consultant
 *
 * SourceBits Technologies
 * 63, 19th Main
 * Rajajinagar 2nd Block
 * Bangalore, KA, India
 *
 * Ph  +91 80 4127 7434
 * Mob +91 97 4237 6432
 * Fax +91 80 2342 5494
 * www.sourcebits.com
  */

On Thu, Sep 4, 2008 at 1:33 AM, Andrew Sledge <andrew.j.sledge@gmail.com> wrote:

Zend gives you the ability to create relation mapping classes for
implementing them in large scale applications.  For instance, I am
working on a project that involves an enterprise management system
(service desk ticketing, knowledge base, asset management) which is
fairly large scale.  Here I am using ORM.  In the couple of blogging
applications I developed to learn Zend, I used direct database calls.
It really depends on your needs.  If calling the database directly
suits you, then do it!

On Wed, Sep 3, 2008 at 10:00 AM, Jigal sanders <jigalroecha@gmail.com> wrote:
> Hello everyone.
>
> I'm confused. First I thought about writing my own class to talk to my
> (mysql) database. But then I thought, what Am I doing? Zend is actually
> doing this for me.  So then i tried several things. And I ended up by just
> writing my full sql statement and then using $this->db->fetchAll($sql); But
> I have the feeling that this is not what Zend_Db  was aiming for. I read in
> several places that the use of Zend_Db_Table is preferable.
> Can someone please help me out and thell me what the best thing is to do?
>
> Thanks in advance.
>
> J. Sanders
>

--
Andrew Sledge