StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6956210
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-05T12:24:56.210
FavoriteCount
0
LastActivityDate
2011-08-05T12:24:56.210
LastEditDate
LastEditorUserId
0
OwnerUserId
472104
ParentId
6954899
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
If you're willing to take this approach you should probably scan the filed for the mathing string and then <code>include</code> the right one. In the same situation I attempted a different approach. I'm extending the module with new methods, @@registering them so that I won't register two identically named methods. So far it works good, though the project I started is nowhere near leaving the specific domain of one tangled mess of a particular web-site. This is the main file. <pre><code>module Onigiri extend self @@registry ||= {} class OnigiriHandlerTaken < StandardError def description "There was an attempt to override registered handler. This usually indicates a bug in Onigiri." end end def clean(data, *params) dupe = Onigiri::Document.parse data params.flatten.each do |method| dupe = dupe.send(method) if @@registry[method] end dupe.to_html end class Document < Nokogiri::HTML::DocumentFragment end private def register_handler(name) unless @@registry[name] @@registry[name] = true else raise OnigiriHandlerTaken end end end </code></pre> And here's the extending file. <pre><code># encoding: utf-8 module Onigiri register_handler :fix_backslash class Document def fix_backslash dupe = dup attrset = ['src', 'longdesc', 'href', 'action'] dupe.css("[#{attrset.join('], [')}]").each do |target| attrset.each do |attr| target[attr] = target[attr].gsub("\\", "/") if target[attr] end end dupe end end end </code></pre> Another way I see is to use a set of different (but behaviorally indistinguishable) classes with a simple decision making mechanism to call a right one. A simple hash that holds class names and corresponding url_matcher would probably suffice. Hope this helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORuby structure for extendable handler/plugin architechture
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSlotos
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. This table or related slice is empty.
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.