Question

In my system, many entities requires to have attachments.

For example, the Mission entity requires its own attachments, also the Activity, Projects and so on.

The question is how to design the Attachments table?

1. Attachment table per entity, like MissionsAttachments, ActivitiesAttachments etc.?
2. One table for all the attachments in the system? if so, what would be the identifiers for each attachment?

Any idea of how can I create a generic attachment table that will serve the whole system?

Answer 1

I would just have one table for attachments and one table to account for the entities. For example:

Entities Table:
==============
EntityId
EntityName

Attachments Table:
=================
AttachmentId
EntityId
Attachment