Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I tend to prefer server-side logic. My reasons are fairly simple:</p> <ol> <li>I don't trust the client; this may or not be a true problem, but it's habitual</li> <li>Server-side reduces the volume per transaction (though it does increase the number of transactions)</li> <li>Server-side means that I can be fairly sure about what logic is taking place (I don't have to worry about the Javascript engine available to the client's browser)</li> </ol> <p>There are probably more -and better- reasons, but these are the ones at the top of my mind right now. If I think of more I'll add them, or up-vote those that come up with them before I do.</p> <p><hr /> Edited, <a href="https://stackoverflow.com/questions/1516852/client-side-logic-or-server-side-logic/1516870#1516870">valya</a> comments that using client-side logic (using Ajax/JSON) allows for the (easier) creation of an API. This may well be true, but I can only half-agree (which is why I've not up-voted that answer yet).</p> <p>My notion of server-side logic is to that which retrieves the data, and organises it; if I've got this right the logic is the 'controller' (C in MVC). And this is then passed to the 'view.' I tend to use the controller to get the data, and then the 'view' deals with presenting it to the user/client. So I don't see that client/server distinctions are necessarily relevant to the argument of creating an API, basically: horses for courses. :)</p> <p>...also, as a hobbyist, I recognise that I may have a slightly twisted usage of MVC, so I'm willing to stand corrected on that point. But I still keep the presentation separate from the logic. And that separation is the plus point so far as APIs go.</p>
    singulars
    1. This table or related slice is empty.
    1. POClient-side logic OR Server-side logic?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USDavid Thomas
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTDownMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt's interesting that I got four up-votes and a down-vote for this; I'd be interested if the person that down-voted would/could explain? That way the answer becomes either *less wrong*, or *more useful*.
      singulars
      1. PO
      1. USDavid Thomas
    2. COI didn't downvote (drive-by downvotes without explanation irritate me too), but I would guess it's because it is important to validate both client and server side.
      singulars
      1. PO
      1. USEric J.
 

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