2👍
SOLVED
So when I ran the migrate command on heroku bash I noticed that the error was occuring arround here
Applying contenttypes.0001_initial... OK
Applying auth.0001_initial... OK
Applying admin.0001_initial... OK
Applying admin.0002_logentry_remove_auto_add... OK
Applying admin.0003_logentry_add_action_flag_choices... OK
Applying contenttypes.0002_remove_content_type_name... OK
Applying auth.0002_alter_permission_name_max_length... OK
Applying auth.0003_alter_user_email_max_length... OK
Applying auth.0004_alter_user_username_opts... OK
Applying auth.0005_alter_user_last_login_null... OK
Applying auth.0006_require_contenttypes_0002... OK
Applying auth.0007_alter_validators_add_error_messages... OK
Applying auth.0008_alter_user_username_max_length... OK
Applying auth.0009_alter_user_last_name_max_length... OK
Applying auth.0010_alter_group_name_max_length... OK
Applying auth.0011_update_proxy_permissions... OK
Applying products.0002_auto_20200626_0112...Traceback (most recent call last):
File "/app/.heroku/python/lib/python3.6/site-packages/django/db/backends/utils.py", line 86, in _execute
return self.cursor.execute(sql, params)
psycopg2.errors.InvalidParameterValue: NUMERIC precision 10000 must be between 1 and 1000
This line :
Applying products.0002_auto_20200626_0112…Traceback (most recent call last):
So I went to my migration folder and checked out the 0002_auto_20200626_0112 migration. Turned out that I had set max_length in decimal field at 10000. Even though I changed and applied migration before, the very existence of that file was causing error. SO i changed the value on that file manually myself to a value <1000 , >1 and it the error was resolved.
Source:stackexchange.com