|
|
Posted by Tony Rogerson on 12/03/05 19:54
> The most basic principle of a tiered architecture is that display is
> done in the front end and never in the back end. This a more basic
> programming principle than just SQL and RDBMS.
Wrong! Formatting (display) is done where it is most efficient and scalable
to do it. We aren't using mainframes anymore, it matters how much data is
passed between the server and client/middle tier.
The most basic programming principle is that you look at your architecture
and design for what you have and not implement definitive statements likes
yours willy nilly.
Consider - paging, pivoting etc.... is it really efficient to pass back a
million rows to the client just to get the second page of 50 rows? Nope, it
isn't - but thats what your statement proposes.
--
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"--CELKO--" <jcelko212@earthlink.net> wrote in message
news:1133616462.488819.190070@g14g2000cwa.googlegroups.com...
> The most basic principle of a tiered architecture is that display is
> done in the front end and never in the back end. This a more basic
> programming principle than just SQL and RDBMS.
>
> You might also ask why Stock , StockDescriptions, and StockQuantities
> are all split into their own tables when they are clear attributes of a
> stock item. This design flaw is called atrribute splitting for obvious
> reasons.
>
Navigation:
[Reply to this message]
|