Multiple FK poiting to single column I'm working on a project, I'm not an advanced backend/database dev, but I always like to understand the 'why's, pros and cons' of things. So I have this table and some times I use Foreign Keys to relate one table to another.
One thing my client asked me recently was to implement a way to know wich user created each record on the table. Doesn't matter if it's a product, category, address, purchase, client, whatever. He wants to know who created those records.
To do that, I implemented one more field on these tables and I called it author_id, this id is reference the id on the main user table.
The problem is, If I go to the table tb_product and create one FK pointing to tb_user.id I can't do the same on the tb_category. Same applies to all the other tables that are referencing the user ID to be the author of that record.
I could go around this issue by changing the name of the following FK declarations, ex:

fk_product_author_id
fk_category_author_id
fk_address_author_id
and so on...

But my question is.. Is it ok to do that? Is it the correct way to declare all those fk? Or should I do something completely different?
You should choose a pattern for the FK name that respects the relationships between the tables.
My preference is FK_&lt;child entity&gt;_&lt;verb phrase&gt;_&lt;parent entity&gt;.
So fk_product_modified_by_user, fk_category_modified_by_user, etc.