StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
125968
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-09-24T08:09:17.833
FavoriteCount
0
LastActivityDate
2008-09-24T08:09:17.833
LastEditDate
LastEditorUserId
0
OwnerUserId
1174
ParentId
124360
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
Whether something is the 'best' solution really depends on what the problem is you're trying to solve. In some cases the best solution will be the most lightweight solution, in other the most heavyweight. <a href="http://backgroundrb.rubyforge.org/" rel="noreferrer">BackgroundRb</a> is probably the most fully-featured Rails background job processor, but it's also the most complicated so will require more investment to get to grips with it. BackgroundRb can probably handle most use cases, from the simple to the complex. I have heard very good things about Ara T. Howard's <a href="http://codeforpeople.rubyforge.org/svn/bj/trunk/README" rel="noreferrer">Background Job</a> (Bj) which, to quote the README is a brain dead simple zero admin background priority queue for Rails. This is a much more lightweight solution and may be preferable to BackgroundRb for a majority of scenarios as a result. If all you want is a solution for infrequent offline batch-style processing then <a href="http://wiki.rubyonrails.org/rails/pages/RunnerScript" rel="noreferrer"><code>script/runner</code></a> which comes with all Rails apps would be more than adequate. For further reading you might want to look at <a href="http://wiki.rubyonrails.org/rails/pages/HowToRunBackgroundJobsInRails" rel="noreferrer">HowToRunBackgroundJobsInRails</a> from the <a href="http://wiki.rubyonrails.org/rails" rel="noreferrer">Rails Wiki</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is the best way to run asynchronous jobs in a Rails application?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USOlly
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.