Re: Paged Results Set in MySQL DB with one result
| From: | Jochem Maas | Date: | Fri, 05 May 2006 04:16:22 +0000 |
| Subject: | Re: Paged Results Set in MySQL DB with one result | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-235610@lists.php.net to get a copy of this message | ||
Richard Lynch wrote:
On Thu, May 4, 2006 10:15 am, Edward Vermillion wrote:...On May 4, 2006, at 4:16 AM, Richard Lynch wrote:On Wed, May 3, 2006 6:57 pm, Jochem Maas wrote:
Yes. Usually. Mostly sometimes. For something like a Forum or a CMS with minimal EZ tags for the admin on a small-scale site, I'll confess to just tossing HTML into the db. But not if my site is allegedly a professionally-written series of articles.lets assume that the author of the articles what some kind of stylistic and/or semantic control over the content of the article - how would you store this formatting information? I'd hazard to say that XHTML is a rather better markup language definition than any custom thing we could come up with on own own, no?
lol - don't forget the "chunk it so we sell more banners AND link random words in the article to DHTML popup ads" - I *really* hate those.As a personal note, I prefer to read things that have been broken up into logical chunks for me, as opposed to being fed some 2000 word essay all at once. I *hate* scrolling. But then I didn't learn to read on a computer screen either.There's truly logical chunks, and there's "we need you to break this into 10 pages so we can sell more ads, okay?" chunks.
Blech.