StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5572226
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-04-06T19:55:37.653
FavoriteCount
0
LastActivityDate
2011-04-06T20:02:04.933
LastEditDate
2011-04-06T20:02:04.933
LastEditorUserId
312814
OwnerUserId
312814
ParentId
5030862
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I found <a href="http://groups.google.com/group/mongomapper/browse_thread/thread/70f0c47549c7defc" rel="nofollow">this post</a>: which was very helpful. He extended HashWithIndifferentAccess to work as a LocalizedString. The only thing I didn't like about it was having to explicly specify the locale when setting it each time -- I wanted it to work more like a string. of course, you can't overload the = operator (at least I don't think you can) so I used <<, and added a to_s method that would output the string of the current locale.... <pre><code>class LocalizedString < HashWithIndifferentAccess def self.from_mongo(value) LocalizedString.new(value || {}) end def available_locales symbolize_keys.keys end def to_s self[I18n.locale] end def in_current_locale=(value) self[I18n.locale] = value end def << (value) self[I18n.locale] = value end </code></pre> end and then I have a class like: <pre><code>class SimpleModel include MongoMapper::Document key :test, LocalizedString end </code></pre> and can do things like <pre><code> I18n.locale = :en a = SimpleModel.new a.test << "English" I18n.locale = :de a.test << "German" puts a.test # access the translation for the current locale I18n.locale = :en puts a.test # access the translation for the current locale puts a.test[:de] # access a translation explicitly puts a.test[:en] puts a.test.inspect </code></pre> and get <pre><code>German English German English {"en"=>"English", "de"=>"German"} </code></pre> so there we go -- this one actually seems to work for me. Comments welcome, and hope this helps someone!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POmongo_mapper custom data types for localization
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USadamnickerson
UserOwnerUserId
1. USadamnickerson
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.