Skip to content

django-auditlog issues, resolve upstream or fork? #377

Description

@robinharms
  • N1-problems on create - it uses post_save and creates a new object per save. (Solution: Create objects at the end of the transaction with bulk create)
  • Doesn't read bulk-create, can that be solved?
  • Stores a lot of unneeded data. (User email!?) And repr of obj!?
  • The changes-field stores repr rather than object data. (There should be hooks to handle this instead.)
  • Relation to user via actor will be blank if user is removed. (Solution: use int field with index, value with persist.)
  • There's really no reason to save previous value, as long as the older records are intact.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions