πŸ“‚ files

The File model represents any file that is uploaded or attached to other elements in the system, like tasks, microtasks, templates, or chat messages. Files are stored in the server filesystem and only

πŸ“‚ files

🧩 Fields:

  • πŸ†” id (Integer): Unique identifier for the file (primary key).

  • πŸ“„ filename (Text): The name of the file (e.g., report.pdf). Required.

  • 🧩 extension (Text): The file extension (e.g., .pdf, .jpg). Required.

  • πŸ“‚ route (Text): The path or location where the file is stored. Required.

  • πŸ•’ creation_date (DateTime): When the file was uploaded or created. Required.

  • πŸ“ last_modified (DateTime): When the file was last edited. Required.

πŸ”— Relationships:

  • πŸ“Œ files_tasks: Links this file to one or more tasks via TasksFile.

  • πŸ“Œ files_templates: Links this file to templates via TemplatesFile.

  • πŸ’¬ files_chat_logs: Attached to messages in chats via ChatLogsFile.

  • 🧠 files_microtasks: Associated with microtasks via MicrotasksFile.

  • πŸ’¬ files_task_comments: Linked to task comments via TaskCommentsFile.

  • πŸ’¬ files_microtask_comments: Linked to microtask comments via MicrotaskCommentsFile.

  • 🧾 activity_logs: Referenced in logs to track file-related actions.

  • πŸ–ΌοΈ group_chats: Used as image previews or attachments in group chats.

Last updated