Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Totally agree with the idea of a service layer, although it really depends on what works for you. </p> <p>Our approach is to use such a layer as essentially a facade for the nuts and bolts underneath - it describes our application API in a way that makes sense to people who have to code against it. Coding against this API hides the user from the things they're not concerned about, such as data storage and retrieval.</p> <p>What we've found nice about this approach is that it makes sense semantically, correct separation of concerns keeps controllers thin and ensures portability of the model (not that I've ever had to make use of that, but who knows), it's easy to test against, it's scalable - we can easily build other layers on top (e.g. web services) etc. etc.</p> <p>I hear where you're coming from as I was there not too long ago. For a long time I was confused about how to implement the model with Zend Framework. I was looking for a convention or someone to describe how it should be done. </p> <p>What I've learnt over time is that there is no correct answer, and this is where ZF has got it absolutely spot on. It just doesn't make sense to prescribe a mechanism when there's no "one size fits all" approach. </p> <p>In summary, there is no "proper" way to implement the model. As I say, I think it's just about finding something that is sensible for your own situation.</p> <p>My advice is to Google for "Zend Framework Service Layer" and read up as much as you can on that - I think that might be of interest to you. A lot of the time you'll end up back at Stack Overflow, but generally there are links out to good blog posts and articles too.</p> <p>Good luck.</p>
    singulars
    1. This table or related slice is empty.
    1. POGeneral Programming: How to implement model logic in MVC?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USiainp999
    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. VTUpMod
    1. COI have implemented a service layer and have seen the advantages. In my case, this was exactly the answer I was looking for, and I absolutely agree with you. It separates all the major components, but it still gives me all the possibilities to have them talk to each other. You might be right that there's no one answer, and that that's just the power of ZF, but that's also what makes it so confusing. I guess I still have to find that out on my own.
      singulars
      1. PO
      1. UShenk
 

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