Issue while Creating Horilla Server on Ubuntu

[umairkhanrind]

I have successfully created a Ubuntu VM and installed prerequisite on it. I have configured .env file with with my mysql database credentials but when i have started the migration its giving me this error.
Can anyone can help me to sortout this issue.

here is my .env database configuration

Database URL

#DATABASE_URL=postgresql://user:password@localhost:5432/dbname

----OR----

Database Configuration

DB_ENGINE=django.db.backends.mysql
DB_NAME=hrm
DB_USER=dbadmin
DB_PASSWORD='Password@123'
DB_HOST=hrmdb.mysql.database.azure.com
DB_PORT=3306

azureuser@hrm:/horilla$ python3 manage.py makemigrations
No changes detected
azureuser@hrm:/horilla$ python3 manage.py migrate
System check identified some issues:

WARNINGS:
employee.Employee: (models.W036) MySQL does not support unique constraints with conditions.
HINT: A constraint won't be created. Silence this warning if you don't care about it.
Operations to perform:
Apply all migrations: admin, asset, attendance, auditlog, auth, base, biometric, contenttypes, django_apscheduler, employee, helpdesk, horilla_audit, horilla_automations, horilla_documents, horilla_views, leave, notifications, offboarding, onboarding, payroll, pms, recruitment, sessions
Running migrations:
Applying base.0002_initial...Traceback (most recent call last):
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 75, in execute
return self.cursor.execute(query, args)
File "/home/azureuser/.local/lib/python3.8/site-packages/MySQLdb/cursors.py", line 179, in execute
res = self._query(mogrified_query)
File "/home/azureuser/.local/lib/python3.8/site-packages/MySQLdb/cursors.py", line 330, in _query
db.query(q)
File "/home/azureuser/.local/lib/python3.8/site-packages/MySQLdb/connections.py", line 261, in query
_mysql.connection.query(self, query)
MySQLdb.OperationalError: (1060, "Duplicate column name 'employee_id_id'")

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "manage.py", line 22, in
main()
File "manage.py", line 18, in main
execute_from_command_line(sys.argv)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/core/management/init.py", line 442, in execute_from_command_line
utility.execute()
File "/home/azureuser/.local/lib/python3.8/site-packages/django/core/management/init.py", line 436, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/core/management/base.py", line 412, in run_from_argv
self.execute(*args, **cmd_options)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/core/management/base.py", line 458, in execute
output = self.handle(*args, **options)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/core/management/base.py", line 106, in wrapper
res = handle_func(*args, **kwargs)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/core/management/commands/migrate.py", line 356, in handle
post_migrate_state = executor.migrate(
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/migrations/executor.py", line 135, in migrate
state = self._migrate_all_forwards(
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards
state = self.apply_migration(
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/migrations/executor.py", line 252, in apply_migration
state = migration.apply(state, schema_editor)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/migrations/migration.py", line 132, in apply
operation.database_forwards(
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/migrations/operations/fields.py", line 108, in database_forwards
schema_editor.add_field(
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/mysql/schema.py", line 107, in add_field
super().add_field(model, field)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 713, in add_field
self.execute(sql, params)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 201, in execute
cursor.execute(sql, params)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 102, in execute
return super().execute(sql, params)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 67, in execute
return self._execute_with_wrappers(
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
return executor(sql, params, many, context)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/utils.py", line 91, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
File "/home/azureuser/.local/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 75, in execute
return self.cursor.execute(query, args)
File "/home/azureuser/.local/lib/python3.8/site-packages/MySQLdb/cursors.py", line 179, in execute
res = self._query(mogrified_query)
File "/home/azureuser/.local/lib/python3.8/site-packages/MySQLdb/cursors.py", line 330, in _query
db.query(q)
File "/home/azureuser/.local/lib/python3.8/site-packages/MySQLdb/connections.py", line 261, in query
_mysql.connection.query(self, query)
django.db.utils.OperationalError: (1060, "Duplicate column name 'employee_id_id'")
azureuser@hrm:~/horilla$

[horilla-opensource]

Hi @umairkhanrind ,
Sorry for the inconvenience caused. We have been recently facing issue with some field attributes and model in MySQL database due to some constraint issue. For the correct working of the system, those constraints were necessary in our case.
We are slowly going to move our system completely to PostgreSQL for future updates.
Will it be possible for you to use a postgresql database for Horilla?

With Regards,
Team Horilla

[umairkhanrind]

Its working perfectly fine with Postgresql. Thanks.