Heres a problem I'm running into.
https://github.com/rails/rails/issues/8087
On Monday, October 29, 2012 10:18:04 AM UTC-7, Santiago Pastorino wrote:
>
> Hi everyone,
>
> Rails 3.2.9.rc1 has been released. If no regressions are found I will
> release 3.2.9 final this Thursday 1st. If you find a
i type: rails g migration AddFieldToTable field:references
result:
class AddFieldToTable < ActiveRecord::Migration
def change
add_column :tables, :field, :references
end
end
there is no migrations there or i type wrong, on pgSQL, rails 3.2
On Wednesday, October 31, 2012 12:01:31 PM UT
Sorry about that... Pocket email.
--
Richard Schneeman
http://heroku.com
@schneems
Sent from the road
On Wednesday, October 31, 2012 at 10:15 AM, Richard Schneeman wrote:
> S w mill wxswcsswxe ce cxssxsqseaxqxxqs six desqssx. W ce cedsdc cx
> dA
>
> --
> Richard Schneeman
> http:
S w mill wxswcsswxe ce cxssxsqseaxqxxqs six desqssx. W ce cedsdc cx dA
--
Richard Schneeman
http://heroku.com
@schneems
Sent from the road
On Wednesday, October 31, 2012 at 6:37 AM, Christopher COCCHI-PERRIER wrote:
> Hi,
>
> Currently I see many applications using custom accept hea
A. S
--
Richard Schneeman
http://heroku.com
@schneems
Sent from the road
On Wednesday, October 31, 2012 at 6:37 AM, Christopher COCCHI-PERRIER wrote:
> Hi,
>
> Currently I see many applications using custom accept headers for their API
> versionning such as application/vnd.foo-v1+json or a
> Shouldn't Rails coerce these new almost standart headers to application/json
> and applicatioin/xml (for previous example) ?
No, because 'application/vnd.foo-v1+json' is not 'application/json.'
The "+foo" convention was actually introduced in RFC3023, specifically
for XML formats. But it's only
Hello, the pull request has been merged and will be in 3.2.9, thanks!
On Wed, Oct 31, 2012 at 8:18 AM, Aliaksandr Rahalevich wrote:
> Hi here. I have one failed spec in my application and it's caused by return
> value from ActiveRecord#update_column method. It looks like this method is
> broken t
Hi here. I have one failed spec in my application and it's caused by return
value from ActiveRecord#update_column method. It looks like this method is
broken to return correct value. Here is my pull request to solve this
problem.
https://github.com/rails/rails/pull/8083
Please take a look on this.
Hi,
Currently I see many applications using custom accept headers for their API
versionning such as application/vnd.foo-v1+json or
application/vnd.bar-3+xml. But when Rails receive such an accept header, it
cannot convert it to a standart Mime::Type and thus causing problems errors
when using
