Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A classic problem - and one that doesn't have one <em>right</em> answer - as always, it depends :-)</p> <p>The core issue is: do I retrieve a user with all its associated information (potentially making it a really big chunk of data being transferred), or do I make multiple calls to retrieve certain parts of information when needed.</p> <p>I typically tend to lean more towards the second option - retrieve only as much data as you need <em>right now</em> - and go back for more if you really need it.</p> <p>In my experience, often times, users will only use certain aspects of your app - so in some cases, someone might need the core user info, plus addresses. In another, another user would require core user info and their permission - or whatever. Hardly ever will someone need all the available data.</p> <p>If you load "on demand", you do incur a bit of additional overhead and time to load the data - but typically, you're saving a lot of time transferring data that you don't need in the end (when you load everything at once).</p> <p>Again: this is really just a "tendency" in my apps - I don't have any cold hard numbers to back up my observations and prove that this is the right way to go. It's just my own "best practice" for most cases.</p> <p>But again: getting this right borders on black magic :-) so you'll probably just have to try one approach and see if it works (or not) and then potentially rearchitect your solution once you have some facts as to how your solution works in real life use.</p>
    singulars
    1. This table or related slice is empty.
    1. POEntity Framework and WCf
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmarc_s
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POEntity Framework and WCf
      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. VTAcceptedByOriginator
    1. COOk, you have answered on half of my question. How does it go with Save method. Should this save method take the entire graph [ i am hoping definitely not] or just data related to the form or data that you plan on updating.
      singulars
      1. PO
      1. USNihilist
    2. COIf you retrieve the data in small chunks, you should also save it in similarly small chunks, I would think. Only save those parts that actually have any changes - don't save a huge graph, if only a single phone number has changed etc.
      singulars
      1. PO
      1. USmarc_s
    3. COSo say for example on page1 i save User with Address, one page2 just the user, on page 3 i save user with address and phone, Should i then expose three different service methods for save ? like SaveUser SaveUserAndAddress SaveUserAddressandPhone ???
      singulars
      1. PO
      1. USNihilist
 

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