Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think each of the methods you have outlined has its merits and its downsides. Which you choose will be a matter of personal preference, the experiences of those in your team and the type of project - Linq2Sql is great to get up and running quickly but might not be best suited to a large and/or complex enterprise project for example.. the best thing you can do there is try a few and get to know them.</p> <p>As for patterns, they help solve specific and recurring problems in a proven way. They also aid familiarisation for developers who didn't write the code. As above, it is worth trying a few to get a feel for what they do and when to use them - but they solutions to specific programming problems rather than architectural patterns.</p> <p>My typical working process runs:</p> <ul> <li>Create a logical entity model</li> <li>Create the data storage for the entity model</li> <li>Create the data access code and business objects</li> <li>Create the logic / business layer</li> <li>Create the presentation layer</li> </ul> <p>I would typically split Data Access and Business Objects, Business Logic and Presentation (web site / winforms) into their own projects, plus anything that I might want to re-use at a later date also goes in its own project. I also have a Base project containing common extensions and interfaces that I re-use in almost everything I do. </p> <p>In terms of architecture, I try to ensure my projects are loosely coupled so that you can easily move from a three tier to n-tier architecture easily. Loose coupling also means that you can switch your backing store and all you need to do is write a new Data Access layer with all of your logic and presentation code remaining unchanged.</p> <p>I think it's important not to get too hung up on <strong>three</strong> versus <strong>n</strong> tier - if you separate your concerns properly extending your system across multiple tiers at later date will not be a difficult exercise.</p>
    singulars
    1. This table or related slice is empty.
    1. POIdeal .NET Architecture?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USflesh
    1. USflesh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIdeal .NET Architecture?
      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. COYes - I agree regarding LINQ to SQL. I have heard that is not well suited to larger applications. I have delusions of grandeur, so I want an architecture that is robust and scalable. Do you feel that 'n-tier' architecture is the best approach? Out of curiousity, which approach do you use?
      singulars
      1. PO
      1. USKyle Ballard
    2. COTerry - thanks for all the input on this. I chose this answer because of your mention of n-tier and your bulleted steps. If I could also accept annakata's answer I would also. Both are excellent and help me understand better.
      singulars
      1. PO
      1. USKyle Ballard
    3. CONo worries, hope it helps :)
      singulars
      1. PO
      1. USflesh
 

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