Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think there are two things to think about here:</p> <p>One of the worst things you can do is over design, and create a N-Tier system when it isn't needed. If there isn't a need to have a Data Access layer, don't throw one in there.</p> <p>Find out the demands on your system, if you have a need to be able to scale out then you are going to have to design your system in tiers, and use data access methods that are more scalable, as well as services to get/update your data.</p> <p>Second, whether or not you should be throwing these things into a database, as the user adds things to a shopping cart. I don't think this is necessarily an n-teir problem. Trips to the DB are costly, esp when you could just store them client/session side until..</p> <hr> <p>With that being said, I personally like to use a Data Access Layer, I find that it makes code cleaner, and it makes you standardize how you access and change your data. Instead of each class/method being able to change data adhoc, they have to do it through a well defined set of interfaces in the DAO layer that you can control, audit, etc. By using a DAO layer it also helps facility mocking, which is invaluable when it comes to testing.</p> <p>References for N-Teir development:</p> <ol> <li> <a href="http://i.stack.imgur.com/kSTnm.png" rel="nofollow">First just understand what you are trying to accomplish!</a></li> <li><a href="http://www.developerfusion.com/article/3058/boosting-your-net-application-performance/2/" rel="nofollow">What is N-Teir Architecture</a></li> <li><a href="http://weblogs.asp.net/bsimser/archive/2006/08/13/3_2D00_tier-Architecture-wtih-ASP.NET-2.0.aspx" rel="nofollow">Asp.net Tutorial</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/ms978384.aspx" rel="nofollow">MSDN on Application Design (From N-Tier to .NET)</a></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POAn Architectural / Design Pattern Question
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNix
    1. USNix
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAn Architectural / Design Pattern Question
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the reponse Nix. Could you reference me to a good tutorial or a website where N-Tier architecture and stuff like BLL and DAL are explained?
      singulars
      1. PO
      1. USDragan
    2. CO+1 for don't over design
      singulars
      1. PO
      1. UScitronas
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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