Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Is this the the correct way for accessing these variables or should I be doing something differently?</p> </blockquote> <p>You'll find that different people have different opinions about this. The style that I prefer is to have the app delegate pass the necessary information to the first view controller, and have that view controller pass it on to whatever view controllers it creates, and so on. The main reason for this is that it prevents child view controllers from depending on things that they have no business knowing about.</p> <p>If you have some detail editor, for example, you want to be able to pass that editor exactly what it needs to do its work. If you give it that information, the editor is completely flexible -- it'll edit any information that you give it. If the editor knows that it should get its data from some external object, like the app delegate, then it loses some degree of flexibility -- it can <em>only</em> get data from the thing that it knows about.</p> <p>So, it's fine to set up your data model in the app delegate. But when it comes to providing access to the model, think: <strong>tell, don't ask</strong>. That is, have the app delegate <em>tell</em> the first view controller what model object to use, and have that controller <em>tell</em> the next one, and so on. If you have to <em>ask</em>, you have to know <em>who</em> to ask, and that's where the dependencies start heading in the wrong direction.</p> <blockquote> <p>every time I import AppDelegate into a .m file to access these variable's data I feel like I'm doing some wrong.</p> </blockquote> <p>Trust that instinct. Think about <em>why</em> it feels wrong.</p>
    singulars
    1. This table or related slice is empty.
    1. POimporting AppDelegate
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCaleb
    1. USCaleb
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POimporting AppDelegate
      singulars
      1. PTQuestion
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CO+1 Nice way of explaining the destructive nature of dependency buildup.
      singulars
      1. PO
      1. USTill
    2. COGenerally good advice for models in view controllers, but sometimes there's global context information about the _state_ of the app that's not in the model and where it just gets unnecessarily verbose if you pass it from VC to VC to VC. For these cases I find LavaSlider's answer to below to be the most elegant solution.
      singulars
      1. PO
      1. USRhubarb
 

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