have models and all
> of mine always do.
> > >>
> > >> It is more explicit to do so but more importantly they generally
> carry essential real-world information about the relationship itself.
> > >>
> > >> I haven't looked at django-simple histo
I was saying Django's inspectdb will write them for you.M--(Unsigned mail from
my phone)
Original message From: Larry Martell
Date: 20/12/23 00:51 (GMT+10:00) To: django-users@googlegroups.com Subject:
Re: logging admin accesses On Mon, Dec 18, 2023 at 7:23 PM Mike Dewhirst
;>
>> --
>> (Unsigned mail from my phone)
>>
>>
>>
>> Original message
>> From: Larry Martell
>> Date: 19/12/23 08:18 (GMT+10:00)
>> To: django-users@googlegroups.com
>> Subject: Re: logging admin accesses
>>
one)
Original message
From: Larry Martell
Date: 19/12/23 08:18 (GMT+10:00)
To: django-users@googlegroups.com
Subject: Re: logging admin accesses
django-simple-history is close to what we need. The one issue I see
(so far) is that it does not support tab
but it may well
cover m2m tables if you add the models explicitly. --(Unsigned mail from my
phone)
Original message From: Larry Martell
Date: 19/12/23 08:18 (GMT+10:00) To: django-users@googlegroups.com Subject:
Re: logging admin accesses django-simple-history is close to what
;
>>
>>
>> Original message
>> From: Mike Dewhirst
>> Date: 16/12/23 12:38 (GMT+10:00)
>> To: django-users@googlegroups.com
>> Subject: Re: logging admin accesses
>>
>> You seem to be asking for a full history 'system'.
>&g
:38 (GMT+10:00)
> To: django-users@googlegroups.com
> Subject: Re: logging admin accesses
>
> You seem to be asking for a full history 'system'.
>
> I think the Admin history exists to show a bit of history with a link to
> go back to the change form where it happened.
>
> Full
>
> Original message
> From: Larry Martell
> Date: 16/12/23 01:47 (GMT+10:00)
> To: django-users@googlegroups.com
> Subject: Re: logging admin accesses
>
> On Thu, Dec 14, 2023 at 5:49 PM Mike Dewhirst
> wrote:
>
>> Top posting because of phon
)
Original message From: Mike Dewhirst
Date: 16/12/23 12:38 (GMT+10:00) To: django-users@googlegroups.com Subject:
Re: logging admin accesses You seem to be asking for a full history 'system'. I
think the Admin history exists to show a bit of history with a link to go back
to the change
) To: django-users@googlegroups.com Subject:
Re: logging admin accesses On Thu, Dec 14, 2023 at 5:49 PM Mike Dewhirst
wrote:Top posting because of phone email client.Have
you seen the Admin history? Might be already logged for you.Thanks, this is
useful, but it does not seem to be logging
--+-+-+
Shows an add, but not what was added.
So my questions are:
-how can I get it to show the details of what was added or changed
-why are updates to UserInfo and UserExtendProduct shown, but updates to
UserRole are not?
Is that programically accessible? I want to record it in the database.
from django.contrib.admin.models import LogEntry
logs = LogEntry.objects.all() #or you can filter, etc.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
-
> From: Larry Martell
> Date: 15/12/23 06:44 (GMT+10:00)
> To: django-users@googlegroups.com
> Subject: logging admin accesses
>
> Is there a way to capture all admin changes (add, change, delete). I have
> some middleware that gets called on any admin add, change, or delete
Top posting because of phone email client.Have you seen the Admin history?
Might be already logged for you.Mike--(Unsigned mail from my phone)
Original message From: Larry Martell
Date: 15/12/23 06:44 (GMT+10:00) To: django-users@googlegroups.com Subject:
logging admin
Is there a way to capture all admin changes (add, change, delete). I have
some middleware that gets called on any admin add, change, or delete, but I
have not figured out a way to capture specifically what was done, something
like: model, PK, action, e.g.
user, 12, change, first name changed
15 matches
Mail list logo
