← Back to team overview

c2c-oerpscenario team mailing list archive

Re: [Bug 704191] Re: [6.0rc2] Record Modified dialog raised without modification.

 

Hello, just confirming I see that bug on our installations too.

On Tue, Jan 25, 2011 at 3:52 PM, Martin Collins
<704191@xxxxxxxxxxxxxxxxxx>wrote:

> I've upgraded to 6.0.1 and I'm still seeing this. I agree the importance
> is low, it is not actually a problem for me, just something I noticed.
>
> --
> You received this bug notification because you are a member of OpenERP
> Drivers, which is subscribed to OpenERP GTK Client.
> https://bugs.launchpad.net/bugs/704191
>
> Title:
>  [6.0rc2] Record Modified dialog raised without modification.
>
> Status in OpenERP GTK Client:
>  Invalid
>
> Bug description:
>  Similar to https://bugs.launchpad.net/openobject-client/+bug/703712
>  but different I think.
>
>  I had some datetime fields set by datetime.datetime.now().isoformat(' ').
> These would cause the 'This record has been modified do you want to save
> it?' dialog to pop up even when nothing had been changed.
>  I changed isoformat() to strftime() and the problem went away.
>  It seems the fractional seconds that isoformat() adds is causing a
> rounding error or something in the code that checks for modification. I
> don't need the fractions myself but I guess someone somewhere will.
>
>  It took me far too long just to find which fields were at fault. It
>  would be nice to be told which fields have changed in the dialog like
>  in Koo (which no longer works with trunk). Maybe a 'show details' type
>  thing.
>
>
>

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/704191

Title:
  [6.0rc2] Record Modified dialog raised without modification.

Status in OpenERP GTK Client:
  Invalid

Bug description:
  Similar to https://bugs.launchpad.net/openobject-client/+bug/703712
  but different I think.

  I had some datetime fields set by datetime.datetime.now().isoformat(' '). These would cause the 'This record has been modified do you want to save it?' dialog to pop up even when nothing had been changed.
  I changed isoformat() to strftime() and the problem went away.
  It seems the fractional seconds that isoformat() adds is causing a rounding error or something in the code that checks for modification. I don't need the fractions myself but I guess someone somewhere will.

  It took me far too long just to find which fields were at fault. It
  would be nice to be told which fields have changed in the dialog like
  in Koo (which no longer works with trunk). Maybe a 'show details' type
  thing.





References