Databases
StackOverflow2013
Postsdbo
POMVC and ORM - which Model logic goes where?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMVC and ORM - which Model logic goes where?
    primarykey
    data
    text
    <p>For clarity consider a fairly standard "User registration" functionality:</p> <p>My ORM (Propel) allows you to alter the class <em>ormUser</em>, which extends the <em>ormUserBase</em>, in order to introduce custom functionality.</p> <p>Now that I have coupled Propel with an MVC framework I am wondering which logic should go where from a best practice point of view.</p> <p>For my user registration functionality I'd create:</p> <blockquote> <ul> <li><p>RegistrationController - <em>which uses the</em></p></li> <li><p>UserModel - <em>which in turn should call something like</em></p></li> <li>LoginView</li> <li>LogoutView</li> <li>SignupView</li> <li>ProfileView</li> </ul> </blockquote> <p>The <em>user</em> database table is coupled with <em>user-profile</em> and Propel has generated handy methods to work with these tables. But now Propel's standard methods are not sufficient and I need to extend functionality.</p> <p>Where would one do this correctly?</p> <p>Would I only extend <em>ormUser</em> for new query methods and place non-query logic in my <em>UserModel</em>? Or would you simply ignore <em>ormUser</em> and use <em>UserModel</em> for everything custom, calling other <em>ormTableNameClass</em>-s there as needed for my logic?</p> <p>I understand keeping new methods in Propel has the benefit of reusability in other Models and Controllers, but I'm not sure from a "do it correctly" point of view since it seems I need business logic to determine the outcome of certain queries.</p> <p><em>UPDATE:</em> <a href="https://stackoverflow.com/questions/4869336/using-orm-classes-directly-from-the-controller-in-mvc-bad-practice/4884215#4884215">Using ORM classes directly from the controller in MVC, bad practice?</a> shows how one usually works with Propel, which in my mind overlaps the framework's model...</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USMattW
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COIt depends on the type of functionality you want to add. Can you give an example?
      singulars
      1. POMVC and ORM - which Model logic goes where?
      1. USJan-Henk
    2. COSure - say I'd want to create a public "show users profiles alphabetically" view. I would need paging logic and multiple queries, most of which are native to Propel but lets assume here they are not fully covered. Let's say I need logic in the queries itself which is not DB related. Would I create a method in Propel that takes arguments for the paging, executing this method from my Model and working, or would I do it all in my Model?
      singulars
      1. POMVC and ORM - which Model logic goes where?
      1. USMattW
    3. COIn that scenario the controller should retrieve a list of alphabetically ordered user models, and pass this list to the view. The view then constructs the HTML output of the actual list of user profiles. I do not know how Propel works, but you should not add the retrieval logic to the user model. Ideally you would create some sort of user repository class that interfaces with Propel, and that class would be responsible for retrieving user objects from the database.
      singulars
      1. POMVC and ORM - which Model logic goes where?
      1. USJan-Henk
 

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