this occurs when manage does not detect any changes to your project
or if the project folders have lost sync.
I have run into this before lots of times.
this is based on djando 1.11 but should work moving forward in principal.
In general try the following :
syncdb :
No longer exists ....
when creating the database tables do the following :
remove ALL migrations directories in app's
manage makemigrations <appname> DO FOR ALL APPS
manage migrate --fake-initial
manage migrate
manage createsuperuser (optional)
When creating new apps __init__.py must exist
manage migrate --fake-initial <appname> to create the table(s)
the above will not destroy any db tables etc but if you added a field
that never got updated to the database you will probably need to reverse
the table changes (in your model), then sort the migrations out as per
above and then re-add the table entries
This can happen when syntax errors, migrations errors occured on the
last run and it did not make it far enough to add the fields?
hope this helps.
Happy Saturday !!!
Thanks - paul
Paul Kudla
Scom.ca Internet Services <http://www.scom.ca>
004-1009 Byron Street South
Whitby, Ontario - Canada
L1N 4S3
Toronto 416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email p...@scom.ca
On 5/27/2022 4:12 PM, Sabir Ali wrote:
(Hpenv) E:\HealthPrediction>python manage.py makemigrations
_*No changes detected*_
(Hpenv) E:\HealthPrediction>
"No changes detected' what will i do Please help me. I am beginner in
django. Please help me
On Friday, May 27, 2022 at 2:12:09 AM UTC+5:30 dcol...@gmail.com wrote:
I was reading the django docs and i have been confused by the
explanation as shown in the snippet.
Screenshot from 2022-04-29 01-36-59.png
in the first snippet of code does it mean that both conditions will
have to be met as in the case of "and" in logical operators?
Second snippet, do they imply that the blog objects will first be
filtered to have only those that contains "lennon" and then the
results will be filtered again to have only those in year 2008?
Please help
--
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
<mailto:django-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/dd74a081-d8ce-464e-9ae4-5f87d9e849dan%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/dd74a081-d8ce-464e-9ae4-5f87d9e849dan%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
--
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/54e1bf6c-231b-e266-1401-f55cfe9c6a17%40scom.ca.
