[Rails] Re: Re: Re: Re: Re: ActiveRecord 1.13.2 -> 1.14.0 breaks Pos

[Jeroen Houben]

Joe wrote:
> Jeroen Houben wrote:
>> Joe wrote:
>>>> pg functions in them for sure didn't work properly in 1.0 (at least for 
>>>> me)
>>>>
>>>> Jeroen
>>> I just had timestamp columns with defaults of current_timestamp or 
>>> now(). The default was used fine in 1.0, but after switching to 1.1 they 
>>> caused errors.
>> In my case, on 1.0, they would use *the same* timestamp value for each
>> insert/update even if they were hours apart, because rails would cache
>> those defaults somehow.
>>
>> Jeroen
> 
> 
> Oh yeah, I saw that problem in the faults reports. But for me the 
> current timestamp was always added as the default value correctly.

Maybe it only occurred with the magic created_at / updated_at columns. I 
don't think BC breakage is bad per se, as long as it's clear what the 
breakage entails.

Jeroen