Django 5.1.2 Documentationmodels Considerations when removing model fields Data Migrations Squashing migrations Serializing values Supporting multiple Django versions Managing files Using files in models The File object File storage URL paths to Python callback functions (“views”). The path strings use parameter tags to “capture” values from the URLs. When a user requests a page, Django runs through each path, in order, and stops at Python function. Each view gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django0 码力 | 3519 页 | 3.17 MB | 1 年前3- Django 5.1 Documentationmodels Considerations when removing model fields Data Migrations Squashing migrations Serializing values Supporting multiple Django versions Managing files Using files in models The File object File storage URL paths to Python callback functions (“views”). The path strings use parameter tags to “capture” values from the URLs. When a user requests a page, Django runs through each path, in order, and stops at Python function. Each view gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django0 码力 | 3513 页 | 3.17 MB | 1 年前3
Django 5.1.2 DocumentationURL paths to Python callback functions (“views”). The path strings use parameter tags to “capture”values from the URLs. When a user requests a page, Django runs through each path, in order, and stops at Python function. Each view gets passed a request object –which contains request metadata –and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django calls the specified view function with an HttpRequest object as the first argument and any “captured”values from the route as keyword arguments. We’ll give an example of this in a bit. path() argument: kwargs0 码力 | 2923 页 | 9.62 MB | 1 年前3- Django 5.1 DocumentationURL paths to Python callback functions (“views”). The path strings use parameter tags to “capture”values from the URLs. When a user requests a page, Django runs through each path, in order, and stops at Python function. Each view gets passed a request object –which contains request metadata –and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django calls the specified view function with an HttpRequest object as the first argument and any “captured”values from the route as keyword arguments. We’ll give an example of this in a bit. path() argument: kwargs0 码力 | 2917 页 | 9.59 MB | 1 年前3
- Django 5.0.x Documentationmodels Considerations when removing model fields Data Migrations Squashing migrations Serializing values Supporting multiple Django versions Managing files Using files in models The File object File storage URL paths to Python callback functions (“views”). The path strings use parameter tags to “capture” values from the URLs. When a user requests a page, Django runs through each path, in order, and stops at Python function. Each view gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django0 码力 | 3407 页 | 3.21 MB | 1 年前3
- Django 5.0.x DocumentationURL paths to Python callback functions (“views”). The path strings use parameter tags to “capture”values from the URLs. When a user requests a page, Django runs through each path, in order, and stops at Python function. Each view gets passed a request object –which contains request metadata –and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django calls the specified view function with an HttpRequest object as the first argument and any “captured”values from the route as keyword arguments. We’ll give an example of this in a bit. path() argument: kwargs0 码力 | 2878 页 | 9.60 MB | 1 年前3
- Django 4.2.x Documentationmodels Considerations when removing model fields Data Migrations Squashing migrations Serializing values Supporting multiple Django versions Managing files Using files in models The File object File storage URL paths to Python callback functions (“views”). The path strings use parameter tags to “capture” values from the URLs. When a user requests a page, Django runs through each path, in order, and stops at Python function. Each view gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django0 码力 | 3305 页 | 3.16 MB | 1 年前3
- Django 4.1.x Documentationmodels Considerations when removing model fields Data Migrations Squashing migrations Serializing values Supporting multiple Django versions Managing files Using files in models The File object File storage URL paths to Python callback functions (“views”). The path strings use parameter tags to “capture” values from the URLs. When a user requests a page, Django runs through each path, in order, and stops at Python function. Each view gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django0 码力 | 3240 页 | 3.13 MB | 1 年前3
- Django 4.0.x Documentationmodels Considerations when removing model fields Data Migrations Squashing migrations Serializing values Supporting multiple Django versions Managing files Using files in models The File object File storage URL paths to Python callback functions (“views”). The path strings use parameter tags to “capture” values from the URLs. When a user requests a page, Django runs through each path, in order, and stops at Python function. Each view gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django0 码力 | 3184 页 | 3.14 MB | 1 年前3
- Django 4.0.x DocumentationURL paths to Python callback functions (“views”). The path strings use parameter tags to “capture” values from the URLs. When a user requests a page, Django runs through each path, in order, and stops at Python function. Each view gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django calls the specified view function with an HttpRequest object as the first argument and any “captured” values from the route as keyword arguments. We’ll give an example of this in a bit. path() argument: kwargs0 码力 | 2248 页 | 7.90 MB | 1 年前3
共 87 条
- 1
- 2
- 3
- 4
- 5
- 6
- 9