StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4749472
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-01-20T16:05:55.393
FavoriteCount
0
LastActivityDate
2011-12-21T11:00:12.650
LastEditDate
2011-12-21T11:00:12.650
LastEditorUserId
534005
OwnerUserId
372981
ParentId
4692939
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
The best approach in Rails 3 is using the built-in mechanism, <a href="https://github.com/svenfuchs/i18n" rel="nofollow">the I18n gem</a>. I am not sure if I understand you problem with the DB data. If you define the categories in the database, just add an i18n key to them and in the model return the translated title. e.g. <pre><code>class Category # with a column that holds the i18n_lookup_key (maybe you think of a better name) ... def translated_title I18n.translate(i18n_lookup_key) end end </code></pre> you then can use the translated_title method for displaying the category's title. If you have more questions about I18n in Rails, we just did a series on our blog: <a href="http://hemju.com/2011/01/13/internationalization-i18n-api-in-rails-3-part-i/" rel="nofollow">Internationalization (I18n) API in Ruby on Rails 3 (Part I)</a> <ul> <li>Definition of Internationalization & Localization</li> <li>How i18n mechanism works in Rails</li> <li>Setup/Configuration about the i18n mechanism</li> <li>Using the I18n with interpolation</li> <li>Using the I18n with pluralization</li> </ul> <a href="http://hemju.com/2011/01/20/internationalization-i18n-api-in-rails-3-part-ii/" rel="nofollow">Internationalization (I18n) API in Ruby on Rails 3 (Part II)</a> <ul> <li>Localization of Times/Dates</li> <li>Using views for translation</li> <li>Translating ActiveRecord errors</li> <li>Organization of resource files</li> <li>Setting the Locale from the Domain Name</li> <li>Setting the Locale from the URL Params</li> </ul> <a href="http://lingui.st/2011/09/internationalization-i18n-api-in-ruby-on-rails-3-part-iii/" rel="nofollow">Part 3 is coming out next week, with a PDF including all the topics.</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails 3 I18n approaches
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmurrekatt
UserOwnerUserId
1. UShjuskewycz
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORails 3 I18n approaches
 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
 VTAcceptedByOriginator
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. COUnfortunately, the links are dead.
 singulars
 PostPostId
 PO
 UserUserId
 UStessi

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.