Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First off, the reason the analyzer is complaining is because you're creating your <code>Hexagram</code> object via <code>alloc] init</code>, and returning it like that, which means your object will start out with a retain count of 1. Unless your method names starts with new/alloc/copy, the user of the code (and static analyzer) will be expecting an autoreleased object. (See <a href="https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/MemoryMgmt/Articles/mmRules.html" rel="nofollow">documentation of naming conventions + memory management</a>).</p> <p>As for autorelease; Autorelease will give an object a retain count of 1 (so that it can hang around for a bit), but will be released at the end of a run loop. This will cause a retain count of 0, and the object gets deallocated.</p> <p>Now, why does <code>return [current autorelease]</code> fail? The reason will be because of the caller of the method <code>getHexagramforId</code>. If someone is calling a method that returns an autoreleased object (a method that does not start with new/alloc/copy etc...), then it <strong>is their responsibility</strong> to keep hold of that object when it needs to (for the reasons mentioned above).</p> <p>So for example, if you changed <code>return current</code> to <code>return [current autorelease]</code>, and called the method as so:</p> <pre><code>Hexagram* obj = [[SomeClass getHexagramforId:3] retain]; </code></pre> <p>your program shouldn't crash. You are explicitly retaining an autoreleased object, so you now can keep that object around, until you no longer need it. At that point, call <code>[obj release]</code>.</p> <p>Other methods for retaining an autoreleased object include assigning it to a retaining property, as so:</p> <pre><code>@property (nonatomic, retain) Hexagram* hexObj; self.hexObj = [SomeClass getHexagramForId:3]; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POanalyzer and autorelease issues with custom objects
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USWDUK
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POanalyzer and autorelease issues with custom objects
      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. VTAcceptedByOriginator
    1. COso is there an alternative to the alloc]init thing? it should be like a class method in the Hexagram class?
      singulars
      1. PO
      1. USAndres Bucci
    2. COYou'd be deferring the `alloc]init`; every object gets created using `alloc]init` at some point in their life, but to abstract that away, some people create class methods to return autoreleased versions. For example `[NSString stringWithString:@"..."]` is the autoreleased version of `[NSString alloc] initWithString:@"..."]`. The autoreleased version will `return [[[NSString alloc] initWithString:@"..."] autorelease];`
      singulars
      1. PO
      1. USWDUK
    3. COAs such, the method I describe in my answer is the best way. Creating `Hexagram` via `alloc]init` is totally fine, and make sure you return the autoreleased version of it. Then, whatever is using the returned object, make sure they retain it.
      singulars
      1. PO
      1. USWDUK
 

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