StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>pros:</strong> <br/>- simple approach and some of the data mapping is done for you with the datatable's. <br/>- offers some conveniences for firing Select, Add, Update and Delete queries. <br/>- might be suitable for very simple design with few tables. <br/>- suitable for non-self-referencing ER degigns or ER's with few lookup tables and simple/few joins <br/>- suitable where simple data store is required. ie. where complex OO ideas should be applied to the "business objects" this pattern would make things more difficult.</p> <p><strong>cons:</strong> <br/>- large OO models will struggle in this pattern <br/>- complex ER designs with many tables, complex relationships or OO object requirements will not fit this pattern. the datatables dont provide much assistance for in-code object querying like LINQ. <br/>- most queries need to be written by hand in SQL (this includes joins). yes, you can use the query designer, but this dont help much. <br/>- there is a lot of code duplication in this approach. as in you will write lots of CRUD methods in your BLL classes (which you also need to write from scratch).</p> <p><strong>conclusion:</strong> it really depends on your requirements. if your implementation is small/simple then this might be a good idea. but growing on a small idea will be hard with this approach. a more OO approach will set you up much better for refactoring/expanding later. this pattern is also older/antiquated. object querying IQueryable/LINQ is more popular and will become a wider standard shortly. i'd suggest u jump on board this wagon. it will be better for your personal development in the long run too. :D</p> <p><strong>some links:</strong></p> <ul> <li>try aspnet MVC - <a href="http://www.asp.net/learn/mvc-videos/video-360.aspx?redir=true" rel="noreferrer">http://www.asp.net/learn/mvc-videos/video-360.aspx?redir=true</a></li> <li><a href="http://www.asp.net/learn/mvc-videos/video-361.aspx?redir=true" rel="noreferrer">http://www.asp.net/learn/mvc-videos/video-361.aspx?redir=true</a></li> <li><a href="http://www.asp.net/learn/mvc-videos/video-395.aspx" rel="noreferrer">http://www.asp.net/learn/mvc-videos/video-395.aspx</a></li> <li>if your scope is bigger, this will be a good start with handy patterns - <a href="http://www.asp.net/learn/mvc-videos/video-350.aspx" rel="noreferrer">http://www.asp.net/learn/mvc-videos/video-350.aspx</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload