4👍
Not all forms are directly related to a Model. While most of the time you might end up using a ModelForm, sometimes you want to create a form for something that is better expressed as an individual form and then you can patch the data together in the view. In my experience this isn’t often, but it happens sometimes.
2👍
Riffing off of Paolo’s answer, if you are collecting data from the user to store in your database, you will probably already have a model set up with fields for the information that needs to be collected. In this case, use a ModelForm
. On the other hand, sometimes you have scenarios where instead of collecting data from the user, you’re using their input to perform some action on data already in the database, perhaps, say, generating a view that’s a mashup of information from multiple models. In this case, you will want to use Form
. The Form
will still allow you to perform validation on the user input comparatively easily.
- [Django]-Ignoring [Django] ERROR (EXTERNAL IP): Internal Server Error
- [Django]-Django: environment variable for SECRET_KEY not working