StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16446732
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-05-08T17:28:43.573
FavoriteCount
0
LastActivityDate
2013-05-08T17:28:43.573
LastEditDate
2017-05-23T12:22:23.407
LastEditorUserId
-1
OwnerUserId
1187415
ParentId
16444504
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
Strictly speaking, there is no "abstract class" or "abstract property" in Objective-C, see for example this thread <a href="https://stackoverflow.com/questions/1034373/creating-an-abstract-class-in-objective-c">Creating an abstract class in Objective-C</a> for a good overview. Your approach is not optimal, because it requires that the superclass implements <code>foo</code> and <code>setFoo:</code>, which contradicts the idea of "abstractness". A better solution is to define a "dynamic property" in the superclass: <pre><code>@interface SuperClass : NSObject @property (strong, nonatomic) Foo *foo; @end @implementation SuperClass @dynamic foo; @end </code></pre> and explicitly synthesize it in the subclass: <pre><code>@interface SubClass : SuperClass @end @implementation SubClass @synthesize foo = _foo; @end </code></pre> Now you can access <code>foo</code> on a subclass object, but on a superclass object it will cause a runtime exception. For lazy initialization, you can use the usual pattern, without any "super-tricks": <pre><code>- (Foo *) foo { if(!_foo) _foo = [[Foo alloc] init]; return _foo; } </code></pre> An alternative approach (also mentioned in above thread) is to use a "protocol" instead of a common superclass: <pre><code>@protocol HasFoo <NSObject> - (Foo *)foo; @end @interface MyClass : NSObject<HasFoo> @property(strong, nonatomic) Foo *foo; @end @implementation SubClass - (Foo *) foo { if(!_foo) _foo = [[Foo alloc] init]; return _foo; } @end </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is the proper way to lazy initialize an abstract property in Objective-C
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USMartin R
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhat is the proper way to lazy initialize an abstract property in Objective-C
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThank you Martin. I am still learning to think in Obj-C. This makes a lot of sense.
 singulars
 PostPostId
 PO
 UserUserId
 USizk

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.