ch honors the hidden field
> property.
>
> (so still a hack!)
>
> Andy
>
> On May 7, 10:01 am, PierreR wrote:
>
> > Thanks for your reply.
>
> > My intention is to use this field as a version/timestamp to implement
> > a form of optimistic locking.
Thanks for your reply.
My intention is to use this field as a version/timestamp to implement
a form of optimistic locking. I need to receive it back from the user
through a form and check it against the current version/timestamp of
the updated record.
I don't think "exclude" will work for me.
mai, 09:23, PierreR wrote:
> That is what I do !
> (another way is to define a custom model field and override the
> "formfield" method).
>
> But ... I cannot get rid off the label in the admin console. That is
> my problem.
>
> Any easy way to remove the lab
24, Daniel Roseman wrote:
> On May 6, 4:48 pm, PierreR wrote:
>
>
>
> > I don't seem to find a good way to have a hidden field in the admin
> > console. I can of course get the hidden field easily but the label is
> > still showing up. This problem is really relat
I don't seem to find a good way to have a hidden field in the admin
console. I can of course get the hidden field easily but the label is
still showing up. This problem is really related to the Admin app.
I have been trying to "hack" the "fieldset.html" but it is not that
easy. "is_hidden" is onl
Hello,
I have been searching the group on the subject but have not managed to
pull a satisfactory solution out of it.
How is the recommended way to implement optimistic locking in the
django admin ?
Let's say I have a version field or timestamp sent to the user-agent
together with the record (t
6 matches
Mail list logo
