[Rails-core] Re: Reasoning for not supporting ruby 1.8.6 in Rails 3.0

2009-09-17 Thread Mukund
MySQL gem 2.8.1 supports Ruby 1.9. On Sep 10, 4:40 am, "Ryan Bigg (Radar)" wrote: > Has anyone tried installing the mysql gem from Rubyforge on 1.9? It's stuff > like that that makes people hesitant to switch to 1.9. Projects on Rubyforge > who's owners have long abandoned it. There needs to be

[Rails-core] Re: "Only get, put, and delete requests are allowed" on an XML request... why??

2009-09-17 Thread Snaggy
sorry I didn't realize I was in the wrong forum.. thanks. On Sep 17, 5:39 pm, Daniel Schierbeck wrote: > Hi, > > First of all, this is the "core" group, meant for discussions on the > development and direction of Rails itself, not a help forum -- there's > a dedicated group for that purpose. > >

[Rails-core] Re: "Only get, put, and delete requests are allowed" on an XML request... why??

2009-09-17 Thread Daniel Schierbeck
Hi, First of all, this is the "core" group, meant for discussions on the development and direction of Rails itself, not a help forum -- there's a dedicated group for that purpose. Second, you should issue your POST to "/things", not "/things/1". Cheers, Daniel On Thu, Sep 17, 2009 at 3:17 PM,

[Rails-core] "Only get, put, and delete requests are allowed" on an XML request... why??

2009-09-17 Thread Snaggy
My app on rails 2.3.2 has a standard scaffold for a resource "thing" I try to create a new "thing" like this: curl -d 'pallone' 'http://0.0.0.0:3000/ things/1'-d '_method=put' -H 'Content-type: application/xml' and I get the error "Only get, put, and delete requests are allowed" why? It's

[Rails-core] Re: Nested Attributes does not match documented behavior

2009-09-17 Thread Eloy Duran
> My feeling is that this is a documentation error in NestedAttributes > since the real behavior is that you do have to call reload. Indeed. > Although, it would be nicer if users did not have to remember to > call reload as that would go along with the principle of least > surprise. Maybe