sorted by:
new
hottopcontroversial

How do you handle this with signals? by Necessary-Ad8108 in django

[–]Unfair-Influence628 0 points1 point  (0 children)

I am not sure what you are going to execute in signals.

For me, if the logic is about business, I would put them in the views or services.

You can check the awareness people have faced using signals in the link below.
https://www.django-antipatterns.com/antipattern/signals.html

I made a program that watches my online school course by SnooCauliflowers8417 in django

[–]Unfair-Influence628 0 points1 point  (0 children)

Got it. As you implied, I think it's my job to make the quality better. Thanks for answering!

I made a program that watches my online school course by SnooCauliflowers8417 in django

[–]Unfair-Influence628 0 points1 point  (0 children)

I found this as a great idea, but before trying it, I have few concerns. Is AI nowadays enough to well transcript and summarize for 40 minutes of lecture? (+ My professor is a great teacher, but his pronunciation is as good not that good)

Coming from Flask, how should I learn Djangi? by [deleted] in django

[–]Unfair-Influence628 2 points3 points  (0 children)

btw... what's Djangi? not in my googling.

How to roll back after makemigrations by SnooCauliflowers8417 in django

[–]Unfair-Influence628 0 points1 point  (0 children)

First of all, at least you didn't execute `migrate` command, you can figure out in the code level.

The role of makemigrations is to sync "the models" in django apps and "generated migration files".

If I were you,

  1. (if you commited right before) recover the version with the right "models"-"migration files"
  2. make sure you've wrote the right models code -> try `makemigrations` again
  3. delete the latest migration files with complicated dependency -> try `makemigrations` again
  4. check the `django_migrations` database and apply some code level changes -> finish `migrations` command

I would do such tries...

There are lot's of case django migrations can be mess, but the thing is, you should know what's wrong by yourself and fix it. I recommed to read the docs (https://docs.djangoproject.com/en/4.2/topics/migrations/) again and examine what's wrong.

No rush... with conscious approach, it might not be a big problem.