StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11634283
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-24T15:31:54.690
FavoriteCount
0
LastActivityDate
2012-07-25T02:48:14.827
LastEditDate
2012-07-25T02:48:14.827
LastEditorUserId
1082743
OwnerUserId
1082743
ParentId
11633017
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Updated Thought about it a little. If you only have a few types of errors, how about doing it like this? In your <code>routes.rb</code>, at the very last line, add a <code>match '/my_segment/*path', :to => 'errors#not_found'</code> This should match any path that is not defined (which normally throws <code>ActionController::RoutingError</code>) and push it to your global error page. You can play with play with the segments wildcard above to get your correct path. This should NOT affect your predefined paths, like <code>mydomain.com/controller1</code>. Below is a more fine grained method of control. This will help you match any errors from <code>mydomain.com/some_controller/bad_params</code> <pre><code>def firstController < ApplicationController def method_in_first_controller # Do something here rescue @error = # Error object here render :template=>"some_error_template", :status => :not_found # In specific action end end def secondController < ApplicationController rescue_from ActiveRecord::RecordNotFound, :with => :rescue_not_found # In secondController def method_in_second_controller # Do something end protected def rescue_not_found @error = # Error object here render :template => 'some_error_template', :status => :not_found end end def ApplicationController rescue_from ActiveRecord::RecordNotFound, :with => :rescue_not_found # Globally protected def rescue_not_found @error = # Error object here render :template => 'application/not_found', :status => :not_found end end </code></pre> Using referrer doesn't seem to get anywhere, sorry for the bad answer yesterday.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to render two different error pages for same error code (e.g. 404) in a single rails application?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDamon Aw
UserOwnerUserId
1. USDamon Aw
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
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.