Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In fact there are two models:</p> <h2>THE OLD MODEL</h2> <p>These model was the model before Objective-C 2.0 and inherited from Mac OS X. It still works, but you should not declare properties to modify the ivars. That is:</p> <pre><code>@interface StrokeWidthController : UIViewController { IBOutlet UISlider* slider; IBOutlet UILabel* label; IBOutlet StrokeDemoView* strokeDemoView; CGFloat strokeWidth; } @property (assign, nonatomic) CGFloat strokeWidth; - (IBAction)takeIntValueFrom:(id)sender; @end </code></pre> <p>In this model you do not retain IBOutlet ivars, but you have to release them. That is:</p> <pre><code>- (void)dealloc { [slider release]; [label release]; [strokeDemoView release]; [super dealloc]; } </code></pre> <h2>THE NEW MODEL</h2> <p>You have to declare properties for the IBOutlet variables:</p> <pre><code>@interface StrokeWidthController : UIViewController { IBOutlet UISlider* slider; IBOutlet UILabel* label; IBOutlet StrokeDemoView* strokeDemoView; CGFloat strokeWidth; } @property (retain, nonatomic) UISlider* slider; @property (retain, nonatomic) UILabel* label; @property (retain, nonatomic) StrokeDemoView* strokeDemoView; @property (assign, nonatomic) CGFloat strokeWidth; - (IBAction)takeIntValueFrom:(id)sender; @end </code></pre> <p>In addition you have to release the variables in dealloc:</p> <pre><code>- (void)dealloc { self.slider = nil; self.label = nil; self.strokeDemoView = nil; [super dealloc]; } </code></pre> <p>Furthermode, in non-fragile platforms you can remove the ivars:</p> <pre><code>@interface StrokeWidthController : UIViewController { CGFloat strokeWidth; } @property (retain, nonatomic) IBOutlet UISlider* slider; @property (retain, nonatomic) IBOutlet UILabel* label; @property (retain, nonatomic) IBOutlet StrokeDemoView* strokeDemoView; @property (assign, nonatomic) CGFloat strokeWidth; - (IBAction)takeIntValueFrom:(id)sender; @end </code></pre> <h2>THE WEIRD THING</h2> <p>In both cases, the outlets are setted by calling setValue:forKey:. The runtime internally (in particular _decodeObjectBinary) checks if the setter method exists. If it does not exist (only the ivar exists), it sends an extra retain to the ivar. For this reason, you should not retain the IBOutlet if there is no setter method.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat happens if I don't retain IBOutlet?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USFreeman
    1. USFreeman
    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. 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. COThe conventional wisdom is that you should not use @property setters in dealloc, because they can have unintended consequences if you've provided your own setter. Instead, you should use `[someOutletVar release]; someOutletVar = nil;` to avoid accidentally alloc'ing something during dealloc.
      singulars
      1. PO
      1. USPaul Scott
 

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