StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10213435
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-04-18T16:07:27.333
FavoriteCount
0
LastActivityDate
2012-04-18T16:07:27.333
LastEditDate
LastEditorUserId
0
OwnerUserId
198424
ParentId
10067354
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
In short - no there no nice clean STI API for what you are trying to accomplish as of right now. I actually looked into that a about a year ago and came to a conclusion that it is not a good idea for several reasons: <ol> <li>If you want to utilize PostgreSQL specific features - you are basically marrying yourself to that DB. Don't get me wrong PostgreSQL is a great DB and I've used it on a number of occasions, but you are going to be stuck with that DB and app design.</li> <li>Most likely if you start using DB specific features you'll either end up implementing them manually ( running some kind of commands on the DB or using GUI) or writing some kind of script that you will have to invoke whenever you are running db:migrate ( you will have to do it if you want to do proper testing). After awhile it becomes cumbersome and annoying.</li> <li>If you find that you are more and more annoyed with, to quote you "painfully wide tables and "type" columns" then: <ul> <li>Your table design needs to be rethought and redone</li> <li>Your models may not be a good candidates for STI</li> <li>You just have to live with it. </li> </ul></li> </ol> Most IT problems really come down to this: Effort vs Benefit. In your case you should ask yourself this question: <ul> <li>How much time do you want to spend on implementing a better STI structure if it will only speed up your raw SQL query by a few seconds? Maybe it's better to write a more explicative SQL query? Most applications don't grow to the size where it really becomes an issue. But it maybe different in your case.</li> </ul> P.S.: Also a quick tip on structuring STI in your app: If you find that you have a lot of models that use STI like a ProductCategory, CommentCategory, PhoneCategory, ClientCategory that all inherit from Cateogory - I tend to organize them in folders inside model directory. Then in application.rb just add a line: <code>config.autoload_paths += Dir[Rails.root.join('app', 'models', '{**/**}')]</code>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPostgreSQL inheritance in ActiveRecord?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USkonung
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPostgreSQL inheritance in ActiveRecord?
 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
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.