Is it ok to have multiple files table for a different entity?

I have two entities A and B. A and B can have multiple files associated to them, each of those files can be a document or an image. Does it make sense to create a_files and b_files tables with the the following structure? id | a_id | url | type(enum) id | b_id | url | type(enum) I thought about creating a generic files table too and then reference it through a/b_files, but it seems to me a kind of over-killing joins.