I just worked this into rails and submitted a pull request:
https://github.com/rails/rails/pull/7155
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To view this discussion on the web visit
On Jul 24, 2012, at 5:42 PM, Jon Leighton wrote:
On 24/07/12 21:29, Matt Jones wrote:
Nope, that's not exactly what I observed; I'll try again. That code *does*
call the create correctly, if there are no users with the correct
first_name. The confusing part to me was that it wasn't
Hiya,
So, what was the impetus behind having ParamsParser create Date and
DateTime objects out of application/json requests? The project I'm on
expects parameters to be received as standard types (bools, numbers,
strings, arrays, and hashes). Rails shouldn't try to convert objects that
are
I'm trying to get some issues either closed or some hard TODO's attached. I'm
looking at this issue and wanted to bring it up to the group:
https://github.com/rails/rails/issues/2899#issuecomment-7257057
Problem:
Production database differs from test environment.
Workaround:
Add
On Wed, Jul 25, 2012 at 11:09:06AM -0700, Josh Bourgeois wrote:
Hiya,
So, what was the impetus behind having ParamsParser create Date and
DateTime objects out of application/json requests? The project I'm on
expects parameters to be received as standard types (bools, numbers,
strings,
