Databases
StackOverflow2013
Postsdbo
POHMVC how to separate the modules?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHMVC how to separate the modules?
    primarykey
    data
    text
    <p>I'm making a leave management (HRM) website. I'm using codeignitor HMVC to build this. Following features are included in this site:</p> <ol> <li>A table to display a summary of leaves.</li> <li>A table for leave types like annual, MC, urgent, other...</li> </ol> <p>I was thinking to create two modules for <strong>leave_summary</strong> and <strong>leave_types</strong>, but my friend told me it is useless. </p> <p>According to HMVC architecture we are trying to create self contained modules for reusability. If I'm creating a different module for leave types, I should be able to reuse it and module itself needs to be self containing. But I can't use leave_types module anywhere else. </p> <p>My friend asked me to put all the leave related stuff in one module called <strong>leave</strong>. This sounds strange to me as I found lots of examples people are trying to separate things out.</p> <p>Do we only need to separate the modules which can be reused in the future (ex: login module, image_gallery module, profile module) and keep all others things inside a one module? (according to the above example I have to keep everything related to leave in a one module ex: leave_type, leave_requests, leave_summary will be placed inside the leave module)</p> <p>What are the benefits I will get, if I separate the leave_type, leave_requests, leave_summary etc... into separate modules?</p> <p>Will I be able to reuse them? If so How?</p> <p>In HMVC model classes and other assets can be exchanged among the modules, so how can I call it a self-contained module or a separate entity as it is depending on another module? (ex: I have to call leave_type module's model class inside the leave_summary module to show the leave type name in a table.)</p> <p>I'm little lost here. Please help me to understand. Thanks a lot!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USThe Dude
    1. USThe Dude
    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. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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