Skip to content

Add null constraints to migration file? #572

Description

@ramhoj

Is there a reason to why the auditable_id, auditable_type, action, audited_changes, version, request_uuid, and created_at fields are nullable? Are there cases where they are indeed created with null values or is it simply to be more flexible in upcoming changes without requiring the user to run a new schema migration?

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