peewee Documentation Release 3.0.0generating avatars using gravatar, and a datetime field indicating when that account was created. Relationship: This is a utility model that contains two foreign-keys to the User model and stores which users "many-to-many" relationship between users. by querying and joining # on different columns we can expose who a user is "related to" and who is # "related to" a given user class Relationship(BaseModel): from/to-user. (('from_user', 'to_user'), True), ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users0 码力 | 319 页 | 361.50 KB | 1 年前3
peewee Documentation
Release 3.5.0generating avatars using gravatar, and a datetime field indicating when that account was created. Relationship: This is a utility model that contains two foreign-keys to the User model and stores which users "many-to-many" relationship between users. by querying and joining # on different columns we can expose who a user is "related to" and who is # "related to" a given user class Relationship(BaseModel): from/to-user. (('from_user', 'to_user'), True), ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users0 码力 | 347 页 | 380.80 KB | 1 年前3
peewee Documentation
Release 3.5.0generating avatars using gravatar, and a datetime field indicating when that account was created. Relationship: This is a utility model that contains two foreign-keys to the User model and stores which users "many-to-many" relationship between users. by querying and joining # on different columns we can expose who a user is "related to" and who is # "related to" a given user class Relationship(BaseModel): from_user multi-column index on from/to-user. (('from_user', 'to_user'), True), ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users0 码力 | 282 页 | 1.02 MB | 1 年前3
peewee Documentation Release 3.4.0generating avatars using gravatar, and a datetime field indicating when that account was created. Relationship: This is a utility model that contains two foreign-keys to the User model and stores which users "many-to-many" relationship between users. by querying and joining # on different columns we can expose who a user is "related to" and who is # "related to" a given user class Relationship(BaseModel): from/to-user. (('from_user', 'to_user'), True), ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users0 码力 | 349 页 | 382.34 KB | 1 年前3
peewee Documentation
Release 3.3.0generating avatars using gravatar, and a datetime field indicating when that account was created. Relationship: This is a utility model that contains two foreign-keys to the User model and stores which users "many-to-many" relationship between users. by querying and joining # on different columns we can expose who a user is "related to" and who is # "related to" a given user class Relationship(BaseModel): from_user multi-column index on from/to-user. (('from_user', 'to_user'), True), ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users0 码力 | 280 页 | 1.02 MB | 1 年前3
peewee Documentation
Release 3.4.0generating avatars using gravatar, and a datetime field indicating when that account was created. Relationship: This is a utility model that contains two foreign-keys to the User model and stores which users "many-to-many" relationship between users. by querying and joining # on different columns we can expose who a user is "related to" and who is # "related to" a given user class Relationship(BaseModel): from_user multi-column index on from/to-user. (('from_user', 'to_user'), True), ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users0 码力 | 284 页 | 1.03 MB | 1 年前3
peewee Documentation Release 3.1.0generating avatars using gravatar, and a datetime field indicating when that account was created. Relationship: This is a utility model that contains two foreign-keys to the User model and stores which users "many-to-many" relationship between users. by querying and joining # on different columns we can expose who a user is "related to" and who is # "related to" a given user class Relationship(BaseModel): from/to-user. (('from_user', 'to_user'), True), ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users0 码力 | 332 页 | 370.77 KB | 1 年前3
peewee Documentation Release 3.6.0generating avatars using gravatar, and a datetime field indicating when that account was created. Relationship: This is a utility model that contains two foreign-keys to the User model and stores which users "many-to-many" relationship between users. by querying and joining # on different columns we can expose who a user is "related to" and who is # "related to" a given user class Relationship(BaseModel): from/to-user. (('from_user', 'to_user'), True), ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users0 码力 | 377 页 | 399.12 KB | 1 年前3
peewee Documentation
Release 3.6.0generating avatars using gravatar, and a datetime field indicating when that account was created. Relationship: This is a utility model that contains two foreign-keys to the User model and stores which users "many-to-many" relationship between users. by querying and joining # on different columns we can expose who a user is "related to" and who is # "related to" a given user class Relationship(BaseModel): from_user multi-column index on from/to-user. (('from_user', 'to_user'), True), ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users0 码力 | 302 页 | 1.02 MB | 1 年前3
Conda 24.7.x Documentationthe diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 4 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 4.6. Developer guide 331 conda, Release 24.7.10 码力 | 808 页 | 4.97 MB | 8 月前3
共 364 条
- 1
- 2
- 3
- 4
- 5
- 6
- 37













