Re: Architecture patterns in PHP
| From: | Nathan Nobbe | Date: | Tue, 30 Dec 2008 18:23:45 +0000 |
| Subject: | Re: Architecture patterns in PHP | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-285239@lists.php.net to get a copy of this message | ||
On Tue, Dec 30, 2008 at 11:07 AM, Robert Cummings <robert@interjinn.com>wrote:
> On Tue, 2008-12-30 at 12:53 -0500, Eric Butera wrote:
> > On Tue, Dec 30, 2008 at 12:42 PM, Nathan Nobbe
> >
> > I was following the blog tutorial on cake and here's what I got from
> > hitting the post/index page:
> >
> > 081230 12:51:55 316 Connect root@localhost on
> > 316 Init DB cake
> > 316 Query SHOW TABLES FROM
cake
> > 316 Query DESCRIBE posts
> > 316 Query SELECT
> > Post.id,
> > Post.title,
> > Post.body,
> > Post.created,
> > Post.modified FROM
> > posts AS
> > Post WHERE 1 = 1
> > 316 Quit
>
> A good framework will allow you to replace the introspection step with a
> static definition of the database table, thus easily bypassing the extra
> queries. Although, I can't fathom why they've requested all the tables.
i think even w/o the static definitions, any sane framework would cache the
schema definition somewhere, at least temporarily to keep performance
reasonable. im not sure if thats the case, in any of these however.
-nathan