Displaying 2 results from an estimated 2 matches for "reload_after_save".
2005 Mar 03
12
bug in postgresql ''now'' time handling??
line 212 of postgresql_adapter.rb is
return Time.now.to_s if value =~ /^\(''now''::text\)::(date|timestamp)/
i don''t think this will work. in postgresql the field ''now'' is pinned to the
SAME TIME for the duration of a transaction. eg. if you do
begin transaction;
insert into t values(42, ''now'');
# sleep one minute
2005 Mar 04
3
Boolean values
...y of Time.now *not* being in UTC if you were expecting it to
>> be.
>
> <snip point conceded>
>
>> Well, how often do you generate reports based on
>>
>> a) unsaved objects
>> b) objects that you *just* saved? Again, if we can get some kind of
>> :reload_after_save business going on, the question becomes moot.
>
> neither really works. again, the problem is that not so much that you are
> doing reports on the unsaved objects, but that you may have contrainsts set up
> in the db that rely on the ''now'' field actually being '...