peewee Documentation Release 2.10.2In the example above the User data was selected as part of the query. For more examples of this technique, see the Avoiding N+1 document. If we did not select the User, though, then an additional query query. This function will eagerly load the related instances specified in the subqueries. This is a technique used to save doing O(n) queries for n rows, and rather is O(k) queries for k subqueries. For example0 码力 | 275 页 | 276.96 KB | 1 年前3
peewee Documentation
Release 2.10.2In the example above the User data was selected as part of the query. For more examples of this technique, see the Avoiding N+1 document. If we did not select the User, though, then an additional query query. This function will eagerly load the related instances specified in the subqueries. This is a technique used to save doing O(n) queries for n rows, and rather is O(k) queries for k subqueries. For example0 码力 | 221 页 | 844.06 KB | 1 年前3
peewee Documentation Release 3.6.0In the example above the User data was selected as part of the query. For more examples of this technique, see the Avoiding N+1 document. If we did not select the User, though, then an additional query selected and joined on User, peewee will automatically resolve the foreign-key for us. Note This technique is discussed in more detail in Selecting from multiple sources. List users and all their tweets0 码力 | 377 页 | 399.12 KB | 1 年前3
peewee Documentation
Release 3.6.0In the example above the User data was selected as part of the query. For more examples of this technique, see the Avoiding N+1 document. If we did not select the User, though, then an additional query selected and joined on User, peewee will automatically resolve the foreign-key for us. Note: This technique is discussed in more detail in Selecting from multiple sources. List users and all their tweets0 码力 | 302 页 | 1.02 MB | 1 年前3
peewee Documentation Release 3.0.0In the example above the User data was selected as part of the query. For more examples of this technique, see the Avoiding N+1 document. If we did not select the User, though, then an additional query0 码力 | 319 页 | 361.50 KB | 1 年前3
peewee Documentation
Release 3.5.0In the example above the User data was selected as part of the query. For more examples of this technique, see the Avoiding N+1 document. If we did not select the User, though, then an additional query0 码力 | 347 页 | 380.80 KB | 1 年前3
peewee Documentation Release 3.4.0In the example above the User data was selected as part of the query. For more examples of this technique, see the Avoiding N+1 document. If we did not select the User, though, then an additional query0 码力 | 349 页 | 382.34 KB | 1 年前3
peewee Documentation Release 3.1.0In the example above the User data was selected as part of the query. For more examples of this technique, see the Avoiding N+1 document. If we did not select the User, though, then an additional query0 码力 | 332 页 | 370.77 KB | 1 年前3
peewee Documentation
Release 3.5.0In the example above the User data was selected as part of the query. For more examples of this technique, see the Avoiding N+1 document. If we did not select the User, though, then an additional query0 码力 | 282 页 | 1.02 MB | 1 年前3
peewee Documentation
Release 3.3.0In the example above the User data was selected as part of the query. For more examples of this technique, see the Avoiding N+1 document. If we did not select the User, though, then an additional query0 码力 | 280 页 | 1.02 MB | 1 年前3
共 11 条
- 1
- 2













