There is no way to fix this problem ?

Ok. And what if I want to retrieve data from a form, save it in the database and then insert it into a template?

This is a NORMAL Django application

Thanks for your help. I just started with django so I don't know much but I try to improve every day. And it's a bit complicated because I don't speak English.

mates, is it possible call in a viewset more than one serializer? DRF

that's often my approach for doing nitty gritty things with anything django. documentation is great, but browsing source is most informative

And u can help me

Can I send you part of the code so you can see it?

How to add a button in Django admin dashboard ?

I want help for an ai project

https://dpaste.org/L8gU3

https://dpaste.org/L8gU3

https://dpaste.org/L8gU3

I don't success to create a simple model on Django

What's the problem

What's the problem

50% of people here asks invalid questions and never explain the real issue when you ask the problem

After creating my Django project, I created a models.py file in the project directory.Yesuite I created a simple model: from django.db Import Models Person class (Models.model): Last_name = models.charfield (max_length = 30). Then I added the directory or is my models.py script and when I run the command: Python Manage.py MakeMigrations There is no error, here is the message of the console: NO Change Detected. Django does not execute my migrations and yet there is no error message

You should create model.py inside an app, not in project directory. After that add your app to settings.INSTALLED_APPS

After creating my Django project, I created a models.py file in the project directory.Yesuite I created a simple model: from django.db Import Models Person class (Models.model): Last_name = models.charfield (max_length = 30). Then I added the directory or is my models.py script and when I run the command: Python Manage.py MakeMigrations There is no error, here is the message of the console: NO Change Detected. Django does not execute my migrations and yet there is no error message

What's your app name ?

Use python.py makemigration yourappname

Use python.py makemigration yourappname

Use this

Or send settings.py file

Use this

It does not always work, here is the message of the console: NO Change Detected

Did you deleted some migrations files before?

No no

Add a new field to the same model and try again if it detects the changes

when I created my project Django there was no models.py file

when I created my project Django there was no models.py file

Try django-admin startapp app-name

Try django-admin startapp app-name

That normally came with an models.py

I have created project with that method

Did you try after startproject?

So weird 😭 I get stuck

No

You must first start a project and then an app

You're confusing project with app

😂😂😂😂😂😂😂 thankful you are right 😁😁😁😁😁, I am one of the most stupid computer scientist in the world 😄

https://t.me/django/253614

if i wanna to create model and i include many fields then i have to put any one field to be a primary key?

By default if a primary key is not added to a model Django have a default field pk that stands as an Id for each data stored in that model but production wise I don't think that's a great idea it's better to have an id column with uuid values then assign primary key to it

Why is it better? In case of migration or what?

The uuid value is not predictable you can also use other means but I'm just saying its not a good idea using Django default auto field as an id in production

Why not? Some specific reasons?

it has random value

UUID Globally unique. e.g. No false positive for finding items using log. Easy for migrating data between systems since collision is only theoratically possible. Stateless, it can be generated on the fly. A sense of secure since malicious user can't guess the ID. Not naturally sortable according to creation time. Not readable. Django default id/auto increment Readable. This is especially valuable if we would expose it externally. Thinking of issue id, obviously, issue-123 is much more readable than issue-b1e92c3b-a44a-4856-9fe3-925444ac4c23. Less space. UUID always occupies 16 bytes. It can't be generated on the fly. Instead, we must consult the database to figure out the next available primary key. Some business data can be exposed, since the latest ID could represent the total number of inventory. Attackers can also scan the integer range to explore leakage (though it shouldn't happen if ACL is implemented correctly). It can't be used in the distributed system since it's quite likely that different hosts could produce exactly the same number.