Databases
StackOverflow2013
Postsdbo
PODatabase layer design
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODatabase layer design
    primarykey
    data
    text
    <p>I have design level question in one of my project.I'm working on a project in which I need to fetch some objects using REST. Say for example fetch Customers and show it in a list.</p> <p>Following operations that can be done on Customer,</p> <ul> <li>Adding a Customer</li> <li>Editing Customer details</li> <li>Delete Customer</li> </ul> <p>So I thought of including a Class named 'CustomerManager', included following methods, </p> <pre><code> @interface CustomerManager - (CustomerManager *)sharedManager; - (BOOL)addCustomer:(Customer *)customer; - (BOOL)deleteCustomer:(Customer *)customer; - (BOOL)updateCustomer:(Customer *)customer; @end @implementation CustomerManager - (BOOL)addCustomer:(Customer *)customer; { NetworkManager * manager = [NetworkManager manager] addCustomer:customer ]; } @end </code></pre> <p>In the ViewController where ever I need to perform customer related operations, I used to make it like this,</p> <pre><code> Customer * manager = [Customer sharedManager]; [manager addCustomer:customer]; //fetch customer [manager customers]; //While deleting [manager deleteCustomer:customer]; </code></pre> <p>Everything is looking and working fine, until I get a design level question, why there was a manager in-between . All the work was done on Customer Object, so you need to have all the Customer related operations in the Customer Class, like something below.</p> <pre><code> @interface Customer + (BOOL)addCustomer:(Customer *)customer; + (BOOL)deleteCustomer:(Customer *)customer; + (BOOL)updateCustomer:(Customer *)customer; + (NSArray *)customers; @end </code></pre> <p>The problem here is , even though network related code in a separate class, I need to have a Concrete reference of my network manager in all my model classes. Confused , which one to choose.</p> <p>Which was the best way?. I would like to have some detailed answer for this.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USRJR
    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
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODatabase layer design
      1. USRJR
      1. VTBountyStart
    2. VO
      singulars
      1. PODatabase layer design
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODatabase layer design
      1. This table or related slice is empty.
      1. VTUpMod
    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