Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>here's what i use in the case of a explicit subclass structure:</p> <pre><code>@class MyObject; @interface MONBase : NSObject /* required override */ -(MyObject *)doSomething; /* ... */ @end @implementation MONBase /* ... */ -(MyObject*)doSomething { assert(0 &amp;&amp; "this override is required"); return nil; } @end </code></pre> <p><em>however</em>... protocols are often generally more useful in these and similar cases. the following exhibits one way to achieve this. it implements a protocol and inherits from the shared base -- use derived from the usage in the OP:</p> <pre><code>@class MyObject; @protocol MONProtocol /* required overrides: */ @required - (MyObject *)doSomething; /* optional overrides: */ @optional @end /* base, with shared implementation */ @interface MONBase : NSObject @end @implementation MONBase - (MyObject *)doSomething { /* as long as the sig matches, you won't need to declare it in the interface -- that may be a good thing. you may prefer *not* to implement this, if you favor a runtime exception */ assert(0 &amp;&amp; "this MONProtocol override is required"); return nil; } @end /* subclass of MONBase which extends by implementing MONProtocol */ @interface MONSub : MONBase &lt;MONProtocol&gt; { MyObject* theIvar; /* &lt;&lt; simplest case implementation */ } @end @implementation MONBase /* ... */ - (MyObject *)doSomething { return [[theIvar retain] autorelease]; } @end </code></pre> <p>protocols are nice because they provide many benefits of multiple inheritance, and provide very little dependencies.</p>
    singulars
    1. This table or related slice is empty.
    1. POObj-c noob question regarding subclassing with non-void return type?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USjustin
    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. This table or related slice is empty.
    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