StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7412732
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-09-14T07:28:38.447
FavoriteCount
0
LastActivityDate
2011-09-14T19:37:35.510
LastEditDate
2011-09-14T19:37:35.510
LastEditorUserId
58956
OwnerUserId
58956
ParentId
7412535
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
It has a problem in that you have to remember both to accumulate the points and perform the purchase (and generate the receipt, which is less of a problem as I assume that action has no side effects). In my mind, point accumulation should come automatically when performing a purchase. It's also rather natural that you get a receipt when performing a purchase, so in a way, your initial method was fine, except that it doesn't read very well. If you want a fluent interface I'd introduce an extra class which gently guides the client code into doing the right thing (assuming that all purchases happen with a card and accumulate points the same way): <pre><code>class TravelClub { OngoingPurchase buyAmount(long amount) { return new OngoingPurchase(amount); } private Receipt buyAndAddPointsAndGetReceipt(long amount, long cardNumber){ // make stuff happen } public class OngoingPurchase { private final long amount; private OngoingPurchase(long amount){ this.amount = amount; } public Receipt withCard(long cardNumber){ return buyAndAddPointsAndGetReceipt(long amount, cardNumber); } } } // Usage: Receipt receipt = travelClub.buyAmount(543).withCard(1234567890L); </code></pre> This way, if you forgot to call <code>withCard</code>, nothing happens. It's easier to spot a missing transaction than an incorrect transaction, and you can't get a receipt without performing a complete transaction. Edit: As an aside, it's funny to think that we do all this work to make methods with many parameters readable, when for example named parameters would make the problem go away completely: <pre><code>Receipt r = travelClub.makePurchase(forAmount: 123, withCardNumber: 1234567890L); </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POrefactoring long methods with fluent interfaces
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USgustafc
UserOwnerUserId
1. USgustafc
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
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.