Re: Mapping SQL Result Sets to Browsers

["Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>]

> My take is that you're saying there should be a business 
> objects layer in between?  If so, is that to say that the business 
> objects render as HTML?

Yes, I'm saying there should be a layer in the middle. It's not the
business objects layer's job to know how to generate html, but rather
the web layer's job to know how to generate html based on the business
objects.

The purist in me says there should _always_ be a business object in the
middle. However, the realist in me recognizes that when you're
generating sql on the fly, or even just writing complex sql for
_reporting_ then maybe you'd bypass the business objects. But I will
draw a hard line where reporting means a one-shot, no update, pass at
the db. Truly a report. And even then most reports can be handled
w/business objects. It's the really messy 20-way joins with subselects
and group-bys w/havings where I'll skip the business layer.

-Walden