[Rails] Re: Re: ActiveRecord 1.13.2 -> 1.14.0 breaks Postgres connec

[Jeroen Houben]

Joe wrote:
> Jeroen Houben wrote:
>> Joe wrote:
>>> I'm using Rails 1.1 and Postgres 8.0 and haven't had any connectivity 
>>> problems.
>>>
>>> Only problems with default = current_timestamp...
>> Yes this is a known issue. You don't need now() you can just use
>> created_at and updated_at which will act as automatic timestamps without
>> writing any code for it. If you have any other columns you wish to
>> default to now() you *do* need to set the value explicitly to Time.now()
>> in ruby.
>>
>> Jeroen
> 
> Right. But this strikes me as a MAJOR backwards-compatibility violation. 
> Seems like there was more harm in removing it rather than leaving it in, 
> but I'm not privy to the developers' reasons. It's gonna be a lot of 
> minor editing finding and fixing it in all my Rails apps.

I'm pretty sure this same behaviour was also in 1.0
One important thing to note is that you do not notice this behaviour in 
development mode, so I only found out when I moved to production (on 1.0)

Jeroen