StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow to override default deserialization of params to model object?
primarykey
Id
12750125
data
AcceptedAnswerId
12769191
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-05T16:11:12.847
FavoriteCount
1
LastActivityDate
2015-10-14T11:26:31.133
LastEditDate
2015-10-14T11:26:31.133
LastEditorUserId
990356
OwnerUserId
990356
ParentId
0
PostTypeId
1
Score
1
ViewCount
799
LastEditorDisplayName
text
Body
How to override default deserialization of params to model object? In other words, how to make Rails understand camel case JSON with a snake case database? Example: I receive params <code>Foo</code> object with a field <code>fooBar</code> and I want my <code>Foo</code> model to understand <code>fooBar</code> is in fact database field <code>foo_bar</code>. <pre><code>"Foo": { "fooBar": "hello" /* fooBar is database field foo_bar */ } </code></pre> <pre><code>class Foo < ActiveRecord::Base attr_accessible :foo_bar end class FoosController < ApplicationController def new @foo = Foo.new(params[:foo]) end </code></pre> <code>Foo.new(params[:foo])</code> assumes <code>params[:foo]</code> contains <code>foo_bar</code>. Instead <code>params[:foo]</code> contains <code>fooBar</code> (in my case <code>params</code> contains JSON data). I would like a clean way to handle this case, the same way a model can override <code>as_json</code>: <pre><code>class Foo < ActiveRecord::Base attr_accessible :foo_bar, :another_field def as_json(options = nil) { fooBar: foo_bar, anotherField: another_field } end end </code></pre> There is a <a href="http://apidock.com/rails/ActiveModel/Serializers/JSON/from_json" rel="nofollow"><code>from_json</code> method inside ActiveModel</a> but it is not called when <code>Foo.new(params[:foo])</code> is run. I've read several times that overriding <code>initialize</code> from a model object is a terrible idea.
Tags
<ruby-on-rails><ruby><ruby-on-rails-3>
Title
How to override default deserialization of params to model object?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. UStanguy_k
UserOwnerUserId
1. UStanguy_k
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHow to override default deserialization of params to model object?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POHow to override default deserialization of params to model object?
 UserUserId
 USismriv
 VoteTypeVoteTypeId
 VTFavorite
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.