Great and simple.
Thank you Anthony
2017-07-21 22:19 GMT+01:00 Anthony :
> In appadmin, I think all fields are made writable, which means the
> modified_on field should appear in the form - is that what you see? If so,
> the old value will simply be submitted with the form,
In appadmin, I think all fields are made writable, which means the modified_on
field should appear in the form - is that what you see? If so, the old value
will simply be submitted with the form, so the value will not be updated
(unless you manually change it).
The automatic update will only
For this simple test
db.define_table('tab1',
Field('name'),
auth.signature
)
i got to admin and create a record
Initially the record is saved with modified_on as 2017-07-21 16:21:36
then via admin i edit the record and change name field and save.
The modified_on is still with 2017-07-21
We probably need to see more code and an exact description of the workflow
to make the update and check whether it was applied.
Anthony
On Tuesday, June 27, 2017 at 5:02:04 AM UTC-4, Ramos wrote:
>
> Yes anthony i meant modified_on ,not update_on
>
> I have this code
>
>
Yes anthony i meant modified_on ,not update_on
I have this code
table[id]=dict(field1=1,field2=2)
the row is updated but the *modified_on* is not.
Regards
2017-06-26 19:48 GMT+01:00 Anthony :
> auth.signature includes a modified_on field, not an update_on field.
>
>
auth.signature includes a modified_on field, not an update_on field.
Also, if you update a record by making changes to the row object and then
calling row.update_record() (with no arguments), it will update the record
with all the existing values (so modified_on will not be changed).
Anthony
6 matches
Mail list logo