Re: Mapping SQL Result Sets to Browsers

Walden,

Thanks for the reply. Regarding mixing two layers that "should never be mixed", are you opposed to reading an SQL cursor and writing it directly to the screen? 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?

Nathan M. Andelin


On Wed, Jul 2, 2008 at 1:18 PM, Walden H. Leverich wrote:

Say the application is simple as prompting the user to enter a name. Then generating a list of people having that name (or name prefix) from

your database.

You're mixing two layers that should never be mixed! With the exception
of complex reporting where you're building SQL on the fly, I would have
a business objects layer in the middle. Since you asked how we do it in
other technologies... In .NET we'd:

string firstName = "bob"; //Get it however

Customer example = Customer.NewCustomer();
example.FirstName = firstName;
List<Customer> customers = Customer.GetByExample(example);

At this point I have a list of customers OBECTS whose firstName is Bob.
Of course you need to have a mature object infrastructure in place, but
that's what you should be aiming for anyway.

-Walden

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)