Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Each class should have one designated initializer. When subclassing, you will typically elect the initializer that contains the most custom parameters, and term it your 'designated'. The important part is that all other initializers (to include, in particular, the default initializer described for the parent classr), call up to this initializer. Only the 'designated' initializer calls super, all others call self.</p> <p>For example:</p> <pre><code>//The default initializer documented by Apple for a given class: - (id)init { self = [super init]; return self; } </code></pre> <p>So, let's say you have several initializers with various options:</p> <p>This custom init has the most parameters, and is your new 'designated'. You'll notice that it calls [super init]:</p> <pre><code>- (id)initWithParamters:(NSObject *)paramterOne andParameter:(NSObject *)paramterTwo { self = [super init]; if (self) { __ivarOne = paramterOne; __ivarTwo = parameterTwo; } return self; } </code></pre> <p>You have an additional custom init, but only takes one parameter. Notice that it calls self (NOT super):</p> <pre><code>- (id)initWithParamter:(NSObject *)parameterOne { return [self initWithParamter:parameterOne andParameter:nil]; } </code></pre> <p>Finally, override the classes default initializer (as specified in documentation):</p> <pre><code>- (id)init { return [self initWithParamter:nil]; } </code></pre> <p>To summarize: You may implement as many custom initializers as you'd like in your subclass. One initializer should be deemed your "designated" initializer, and only this method should implement [super init] (where init is the designated initializer of the super class, which may not be 'init'). All the other initializers should call [self init] (where init is the designated initializer for your subclass).</p>
    singulars
    1. This table or related slice is empty.
    1. POSubclassing NSWindowController, can I supply multiple init methods?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USisaac
    1. USisaac
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSubclassing NSWindowController, can I supply multiple init methods?
      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. VTUpMod
    1. COMostly clear now, except for that last bit about calling the super's DI. I see many NSWindowController subclassed with an init method which in turn calls [super initWithWindowNibName], whereas initWithWindow would be the super's DI. So is that incorrect implementation?
      singulars
      1. PO
      1. USYohst
    2. CO@Yohst, yes, I can see where that might be confusing. In the template methods, each method is written as if the others don't exist. I believe this is because the expectation is that they'll only be used discreetly (eg, a given implementation for a class would only use one of them, the others could in theory be removed from the code).
      singulars
      1. PO
      1. USisaac
 

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