@Fred: Thanks a lot, that really helped me!
enrico
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this
Django Field History is a great project to audit trail a model field
On Saturday, January 21, 2017 at 7:19:57 AM UTC-5, enrico baranski wrote:
>
> Hi all Django users,
>
> I'm quite new to Django and currently experimenting with the database
> model. Defining fields appears to be
On Saturday 21 January 2017 04:15:34 enrico baranski wrote:
> I'm quite new to Django and currently experimenting with
the database
> model. Defining fields appears to be quite intuitive and is
well
> described in the documentation. However, I am looking
into audit
> trail fun
Enrico,
In the sample MySQL trigger code of my previous message, you'll
see that I always store, in the primary table, the string username
of the most recent user to update the table. Therefore, that value
is available to the DB trigger as NEW.update_user.
Enrico,
the DB trigger approach sounds very exciting
to me because I really need to be sure that there is no way to
manipulate records without audit trail. I also would be very
interested in the trigger code for MySQL you mentioned.
OK. I'll append
Thinking about this topic more detailed made me realize that I also need to
track the user who performed the insert/change (delete is globally not
permitted) actions. However, that are user names managed via Django ... so
when i use DB triggers I only can track the MySQL user who is used by the
Hi Fed,
the DB trigger approach sounds very exciting to me because I really need to
be sure that there is no way to manipulate records without audit trail. I
also would be very interested in the trigger code for MySQL you mentioned.
You also mentioned that you did something similar
Hi Mike,
thanks for that reference, I will take a look.
Enrico
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To
.
You should still be able to define the audit tables as Django
models,
to get the benefit of schema migrations, etc., and to make it easier
to write an audit trail viewer.
In my case, I didn't have an explicit "version" field in the primary
tables, but
to be quite intuitive and is well
described in the documentation. However, I am looking into audit trail
functionalities. What that means to me. I have two tables, one is my
master data table (rooms) and one is my audit trail table for the
rooms table.
So I aim on two major things, first I
Hi all Django users,
I'm quite new to Django and currently experimenting with the database
model. Defining fields appears to be quite intuitive and is well described
in the documentation. However, I am looking into audit trail
functionalities. What that means to me. I have two tables, one
Hello
Is there a way to have an audit trail record my entry on a https page/
site?
as well as gather the data displayed and update another database for
future data retrieval?
Please be generous with explanations, links, info...
thx
--
You received this message because you are subscribed
No progress so far. I know I can do this:
attrs[field.name] = copy.copy(field)
if attrs[field.name].rel:
attrs[field.name].rel.related_name = "audit_%s_%s" %
(cls.__name__,
field.name)
But this doesn't seem to make a difference. I still get:
Error: One
I'm playing around with the Audit code here:
http://code.djangoproject.com/wiki/AuditTrail
The Caveats section mentions:
Likewise, it fails when there are multiple ForeignKeys? pointing
to the same Model, as it doesn't support / compensate for
related_name.
Does anyone know if this
.
-Larrik Jaerico
On Aug 21, 10:25 am, Sérgio Durand <[EMAIL PROTECTED]> wrote:
> Hi Erick,
>
> It was working on r8339.
> I've updated django this morning to r8460 to and still working !!
>
> What is "history Manager" that you said ?
>
> look how i'm using audi
Hi Erick,
It was working on r8339.
I've updated django this morning to r8460 to and still working !!
What is "history Manager" that you said ?
look how i'm using audit trail:
1) i have my 'ordinary' model (without audit trail feature)
2) i get the audit trail code and drop it
t;
> Finally i've got Audit Trail [1] working again !!! :)
> I'm not a django/python expert (i've started studying 2 months ago), but
> after fighting with "python manage.py validate" and searching in google,
> i've got the solution... the problem basically was missing **
Hi people,
Finally i've got Audit Trail [1] working again !!! :)
I'm not a django/python expert (i've started studying 2 months ago), but
after fighting with "python manage.py validate" and searching in google,
i've got the solution... the problem basically was missing **kwargs
perrito666 wrote:
> Ah thank you, ill keep an eye, so far the only think I did to it was a
> small hack to handle the error raised by trying to copy a fk to the
> audit table but it is a not very clean hack.
> Perrito.
Took me an extra couple of days, but I've got all my modifications to
On 5/15/07, jeffhg58 <[EMAIL PROTECTED]> wrote:
>
> Not sure if many people have used the full history branch. But, I can
> see the ChangeLog information via the admin site. But, when I try and
> get information via the shell
> I get ChangeLog is not defined. Is there something I need to import
Not sure if many people have used the full history branch. But, I can
see the ChangeLog information via the admin site. But, when I try and
get information via the shell
I get ChangeLog is not defined. Is there something I need to import to
be able to recognize the ChangeLog table.
Thanks,
Jeff
Here is my current thinking:
- No changes to main model tables
- Designate a model to be audited by including inner class "Audit"
- One shadow table per audited model
- Generate shadow tables for all audited models on post_syncdb
- Only write to one DB, until multi-db support is
On 4/24/07, robin_percy <[EMAIL PROTECTED]> wrote:
>
> What about doing both? Write a pre_save record indicating the
> operation about to be attempted. And a post_save indicating the
> success of the operation, using a unique identifier to identify the
> pair. Then if the post_save gets out of
What about doing both? Write a pre_save record indicating the
operation about to be attempted. And a post_save indicating the
success of the operation, using a unique identifier to identify the
pair. Then if the post_save gets out of sync, you have a record of
transactions that may be at
On 4/23/07, David Larlet <[EMAIL PROTECTED]> wrote:
>
> It's a bit ugly to declare instance hidden variables (pre) but we need to
> be
> sure that the save/delete is effective (post) before logging it.
>
It's not beautiful, perhaps, but I may end up doing something very similar.
However, one
On 4/21/07, Tim Chase <[EMAIL PROTECTED]> wrote:
>
> Todd Schraml authored a good article in Dr. Dobb's Journal
> (http://www.ddj.com/dept/database/184406340) titled _Table
> Patterns & Changing Data_ where he discusses five patterns for
> keeping historical data, and the requirements that would
On 4/20/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> In your descriptions below, you remove the ability for a developer to
> use manual primary keys, by the sound of it, since one of your special
> fields wants to be a single-column primary key. That's not invisible.
Does Django
2007/4/20, Jason McVetta <[EMAIL PROTECTED]>:
> I need to add real audit trail and change-notification support to an
> existing Django app and to one that is under development. The best way to
> do this, it seems to me, is to add audit support to the Django framework
> itself
> I will be working on this project as part of my Real Job(tm),
> so devoting time to it should not be a problem. However,
> before I begin coding, I want the community's input on a few
> issues.
>
> What is the right way, at DB level, to implement the audit
> trail? I
Hi Jason,
On Fri, 2007-04-20 at 13:30 -0400, Jason McVetta wrote:
> I need to add real audit trail and change-notification support to an
> existing Django app and to one that is under development. The best
> way to do this, it seems to me, is to add audit support to the Django
&g
age that your database provides.
>
> In this manner, any front-end application writing to the database will
> have the audit-trail by default, without need for front-end
> application support.
>
> In other words, I don't believe that the application-level is the
> place to put the audit
I would (and do) implement audit trails right in the database itself
using the trigger and procedure language that your database provides.
In this manner, any front-end application writing to the database will
have the audit-trail by default, without need for front-end
application support
I need to add real audit trail and change-notification support to an
existing Django app and to one that is under development. The best way to
do this, it seems to me, is to add audit support to the Django framework
itself. My requirements are similar to those named by Paul Childs in his
django
33 matches
Mail list logo
