Improve the column naming in database : ({col_name}_id_id) thing

[MahmoudNasser01]

Feature Request

In many columns when it is reflect on the database most of the names have this pattern ({col_name}_id_id) it is pretty annoying.

Description

What I suggest is to make the columns names in django models to be for example department instead of department_id and so one since django add suffix _id by its own

Use Case

[Explain how this feature would be useful and how it fits into the project's context.]

Proposed Solution

What I suggest is to make the columns names in django models to be for example department instead of department_id and so one since django add suffix _id by its own

Benefits

clear database naming

Labels

enhancement

Priority

medium

[horilla-opensource]

Hi @MahmoudNasser01,

Thank you for bringing up this issue and for the detailed explanation, Django automatically adds the _id suffix to foreign key fields, which can lead to redundancy when naming columns in the database, such as department_id_id.

Use Case

We understand that clear and concise naming in the database is crucial for readability and maintenance. Redundant suffixes can cause confusion and clutter, especially when working directly with the database or in raw SQL queries.

Proposed Solution

To address this, we propose leveraging Django's db_column attribute in model fields. This allows us to specify custom column names directly, avoiding the double _id suffix issue. For instance:

class EmployeeWorkInformation(models.Model):
    department = models.ForeignKey(Department, on_delete=models.CASCADE, db_column='department')

This way, the actual database column will be named department instead of department_id.

Next Steps

We'll evaluate the impact of implementing this change across the project and consider including it in future updates. If anyone has additional thoughts or concerns, please share them here.

Thanks again for your suggestion and contribution to improving our project!