Hi,
I am hitting this problem again with new code merges into the
deployment server. Last time, I fixed the issue by doing like this
"I have tried all the ways what you guys suggested me But here I don't want
change database why because it is deployment server so, when I run
manage.py makemigrations migrations are applied and changes are reading but
when I run manage.py migrate changes are not taken to database so, Manually
I queried queries to add columns into respected tables into database."
I really think this might not be a sustainable solution. So, I would really
like to fix this permanently. I would appreciate it if someone could
suggest a remedy for this issue.
Thank you in advance
~Salima
On Tue, Jul 27, 2021 at 5:18 AM guna visva <gunasel...@gmail.com> wrote:
> having had the unfortunate phase of dealing with it , sorting it requires
> some patience
>
> the issue is the tables in django_migrations is not in sync with rest the
> rest of your database or migrations files.
>
> You have to first remove the addition in field etc and make sure the
> database tables are first in sync with your models, then 1. delete
> migrations files and 2. delete django_migrations. Then 3.makemigrations and
> 4. migrate fake. All risks are yours to take
>
> Then finally just add your fields and makemigrations and migrate
>
> The above might/or not work as it might give some content type errors
>
>
>
>
> On Wednesday, July 21, 2021 at 2:39:56 AM UTC+8 sebasti...@gmail.com
> wrote:
>
>> Is in settings.py also in installed app? Without that migrations don't
>> work
>>
>> Salima Begum <sali...@rohteksolutions.com> schrieb am Di., 20. Juli
>> 2021, 19:00:
>>
>>> Hi ,
>>> Thank you for your responses.
>>> I have tried all the ways Which you people suggested I am not getting
>>> any error while running makemigrations or migrate and
>>> python manage.py migrate --fake-initial. But those migrations are not
>>> applying to the database. How can I fix this issue without deleting the
>>> database?
>>>
>>> Thank you
>>> ~Salima
>>>
>>>
>>> On Mon, Jul 19, 2021 at 7:02 PM Aman Vyas <amanv...@gmail.com> wrote:
>>>
>>>> if it is saying no changes detected while running makemigrations and
>>>> you are sure that you changed models.py then these things you can try:
>>>>
>>>> 1: python manage.py makemigrations appname
>>>>
>>>> if this will not work then do that
>>>>
>>>> 2: delete migrations folder from your app and delete database then run
>>>> again python manage.py makemigrations
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Jul 19, 2021 at 6:07 AM Salima Begum <
>>>> sali...@rohteksolutions.com> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I have added a new column to the existing model while developing. Then
>>>>> I run makemigrations and migrate. It is not applied to the database table
>>>>> which is created based on that model. How can I fix this issue? Please
>>>>> help
>>>>> me to complete this issue.
>>>>>
>>>>> The below issue I am facing in deployment server after adding new
>>>>> field and deployed into server.
>>>>>
>>>>> ```
>>>>> psycopg2.errors.UndefinedColumn: column
>>>>> shopping_ls_product_search.quality_prdct does not exist
>>>>> LINE 1: ... Col1 FROM "shopping_ls_product_search" WHERE ("shopping_...
>>>>> ```
>>>>> Thank you
>>>>> ~Salima
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Django users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to django-users...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/django-users/CAMSz6bnLkeN001UnxO3PdCg06Jc%3Dcr22kZXc71KL4w5CbYq_Cw%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/django-users/CAMSz6bnLkeN001UnxO3PdCg06Jc%3Dcr22kZXc71KL4w5CbYq_Cw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Django users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to django-users...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/django-users/CAKZY6%3DAgrWzCmrBHpouSJG_Vfy7i6LQu81Q7EWBRq44Yf3053A%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/django-users/CAKZY6%3DAgrWzCmrBHpouSJG_Vfy7i6LQu81Q7EWBRq44Yf3053A%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-users...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/CAMSz6bmQ5KAQ2SFHCMbf8UHkg34itZPFZ1OksP-2C3t5wAwTJQ%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/django-users/CAMSz6bmQ5KAQ2SFHCMbf8UHkg34itZPFZ1OksP-2C3t5wAwTJQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/f8458021-e0c0-4c30-8188-0c08932b1deen%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/f8458021-e0c0-4c30-8188-0c08932b1deen%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/CAMSz6bki3qrsof6JJC3PhcAGcFECEo-iOttsgXvQ3c2SBcyEWg%40mail.gmail.com.
