Joe wrote:
>  Jeroen Houben wrote:
> > Joe wrote:
> >>> 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
> >> Nah, I never had this problem with 1.0 in production mode. The removal 
> >> of the default code is in the 1.1 changelog for Activerecord.
> > What kind of defaults were you using then, because having defaults with
> > 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
_______________________________________________
Rails mailing list
Rails@[...].org
http://lists.rubyonrails.org/mailman/listinfo/rails