Django 4.2.x Documentationproxy models are intended to behave exactly like the model they are proxying for. They are always in sync with the parent model since they directly inherit its fields and managers. The general rules are: instance of that class represents a particular record in the database table. To create an object, instantiate it using keyword arguments to the model class, then call save() to save it to the database. Assuming we suggest you write your ORM code inside a separate, synchronous function and then call that using sync_to_async - see Asynchronous support for more. Querying JSONField Lookups implementation is different0 码力 | 3305 页 | 3.16 MB | 1 年前3
Django 3.1.x Documentationproxy models are intended to behave exactly like the model they are proxying for. They are always in sync with the parent model since they directly inherit its fields and managers. The general rules are: instance of that class represents a particular record in the database table. To create an object, instantiate it using keyword arguments to the model class, then call save() to save it to the database. Assuming change these assumptions, set the following attributes on your middleware factory function or class: sync_capable is a boolean indicating if the middleware can handle synchronous requests. Defaults to True0 码力 | 3094 页 | 3.03 MB | 1 年前3
Django Q Documentation
Release 0.7.11supported under windows. You should however be able to develop and test without the cluster by setting the sync option to True in the configuration. This will run all async calls inline through a single cluster Defaults to 250 • Failures are always saved. 1.2.8 sync When set to True this configuration option forces all async() calls to be run with sync=True. Effectively making everything synchronous. Useful Tasks 15 Django Q Documentation, Release 0.7.11 sync Simulates a task execution synchronously. Useful for testing. Can also be forced globally via the sync configuration option. cached Redirects the result0 码力 | 54 页 | 412.45 KB | 1 年前3
Django 4.1.x Documentationproxy models are intended to behave exactly like the model they are proxying for. They are always in sync with the parent model since they directly inherit its fields and managers. The general rules are: instance of that class represents a particular record in the database table. To create an object, instantiate it using keyword arguments to the model class, then call save() to save it to the database. Assuming we suggest you write your ORM code inside a separate, synchronous function and then call that using sync_to_async - see Asynchronous support for more. Querying JSONField Lookups implementation is different0 码力 | 3240 页 | 3.13 MB | 1 年前3
Django 4.0.x Documentationproxy models are intended to behave exactly like the model they are proxying for. They are always in sync with the parent model since they directly inherit its fields and managers. The general rules are: instance of that class represents a particular record in the database table. To create an object, instantiate it using keyword arguments to the model class, then call save() to save it to the database. Assuming change these assumptions, set the following attributes on your middleware factory function or class: • sync_capable is a boolean indicating if the middleware can handle synchronous requests. Defaults to True0 码力 | 2248 页 | 7.90 MB | 1 年前3
Django 4.0.x Documentationproxy models are intended to behave exactly like the model they are proxying for. They are always in sync with the parent model since they directly inherit its fields and managers. The general rules are: instance of that class represents a particular record in the database table. To create an object, instantiate it using keyword arguments to the model class, then call save() to save it to the database. Assuming change these assumptions, set the following attributes on your middleware factory function or class: sync_capable is a boolean indicating if the middleware can handle synchronous requests. Defaults to True0 码力 | 3184 页 | 3.14 MB | 1 年前3
Django Q Documentation
Release 0.7.13supported under windows. You should however be able to develop and test without the cluster by setting the sync option to True in the configuration. This will run all async calls inline through a single cluster Defaults to 250 • Failures are always saved. 1.2.8 sync When set to True this configuration option forces all async() calls to be run with sync=True. Effectively making everything synchronous. Useful the cluster’s timeout setting for this task. sync Simulates a task execution synchronously. Useful for testing. Can also be forced globally via the sync configuration option. cached Redirects the result0 码力 | 56 页 | 416.37 KB | 1 年前3
Django Q Documentation
Release 0.7.12supported under windows. You should however be able to develop and test without the cluster by setting the sync option to True in the configuration. This will run all async calls inline through a single cluster Defaults to 250 • Failures are always saved. 1.2.8 sync When set to True this configuration option forces all async() calls to be run with sync=True. Effectively making everything synchronous. Useful the cluster’s timeout setting for this task. sync Simulates a task execution synchronously. Useful for testing. Can also be forced globally via the sync configuration option. cached Redirects the result0 码力 | 56 页 | 415.46 KB | 1 年前3
Django 3.1.x Documentationproxy models are intended to behave exactly like the model they are proxying for. They are always in sync with the parent model since they directly inherit its fields and managers. The general rules are: instance of that class represents a particular record in the database table. To create an object, instantiate it using keyword arguments to the model class, then call save() to save it to the database. Assuming change these assumptions, set the following attributes on your middleware factory function or class: • sync_capable is a boolean indicating if the middleware can handle synchronous requests. Defaults to True0 码力 | 2053 页 | 6.92 MB | 1 年前3
Django 3.2.x Documentationproxy models are intended to behave exactly like the model they are proxying for. They are always in sync with the parent model since they directly inherit its fields and managers. The general rules are: instance of that class represents a particular record in the database table. To create an object, instantiate it using keyword arguments to the model class, then call save() to save it to the database. Assuming change these assumptions, set the following attributes on your middleware factory function or class: • sync_capable is a boolean indicating if the middleware can handle synchronous requests. Defaults to True0 码力 | 2199 页 | 7.89 MB | 1 年前3
共 82 条
- 1
- 2
- 3
- 4
- 5
- 6
- 9













