[Rails] ActiveResource::create with an existing id: Rails 3.0 vs Rails 3.1 and above

2012-12-19 Thread Chuck Han
I'm upgrading my application from Rails 3.0 to Rails 3.2 (yeah, I know, what happened to 3.1?), and I'm experiencing a difference in the REST call when calling ActiveResource::create where the id is already defined. In 3.0, the app is sending a PUT. In 3.1 and above, is sending a POST. The

[Rails] Re: ActiveResource::create with an existing id: Rails 3.0 vs Rails 3.1 and above

2012-12-19 Thread Chuck Han
:52:18 PM UTC-8, Chuck Han wrote: I'm upgrading my application from Rails 3.0 to Rails 3.2 (yeah, I know, what happened to 3.1?), and I'm experiencing a difference in the REST call when calling ActiveResource::create where the id is already defined. In 3.0, the app is sending a PUT. In 3.1