peewee Documentation Release 3.6.0existing records Atomic updates Deleting records Selecting a single record Create or get Selecting multiple records Filtering records Sorting records Getting random records Paginating records Counting records Relationships and Joins Model definitions Performing simple joins Joining multiple tables Selecting from multiple sources Subqueries Multiple foreign-keys to the same Model Joining on arbitrary fields Self-joins Person instead of People. This is a convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable0 码力 | 377 页 | 399.12 KB | 1 年前3
peewee Documentation Release 3.4.0existing records Atomic updates Deleting records Selecting a single record Create or get Selecting multiple records Filtering records Sorting records Getting random records Paginating records Counting records Person instead of People. This is a convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable using a relational databases, if we were to do a join from Person to Pet then every person with multiple pets would be repeated, once for each pet. It would look like this: query = (Person0 码力 | 349 页 | 382.34 KB | 1 年前3
peewee Documentation
Release 3.5.0existing records Atomic updates Deleting records Selecting a single record Create or get Selecting multiple records Filtering records Sorting records Getting random records Paginating records Counting records Person instead of People. This is a convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable using a relational databases, if we were to do a join from Person to Pet then every person with multiple pets would be repeated, once for each pet. It would look like this: query = (Person0 码力 | 347 页 | 380.80 KB | 1 年前3
peewee Documentation
Release 3.4.0Person instead of People. This is a convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable using a relational databases, if we were to do a join from Person to Pet then every person with multiple pets would be repeated, once for each pet. It would look like this: query = (Person .select(Person include wildcards here: query = Facility.select().where(Facility.name ** '%tennis%') Matching against multiple possible values How can you retrieve the details of facilities with ID 1 and 5? Try to do it without0 码力 | 284 页 | 1.03 MB | 1 年前3
peewee Documentation
Release 3.6.0Person instead of People. This is a convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable using a relational databases, if we were to do a join from Person to Pet then every person with multiple pets would be repeated, once for each pet. It would look like this: query = (Person .select(Person number of parameters and return a single value. • Aggregates - which aggregate parameters from multiple rows and return a single value. • Collations - which describe how to sort some value. Note: For0 码力 | 302 页 | 1.02 MB | 1 年前3
peewee Documentation
Release 3.5.0Person instead of People. This is a convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable using a relational databases, if we were to do a join from Person to Pet then every person with multiple pets would be repeated, once for each pet. It would look like this: query = (Person .select(Person number of parameters and return a single value. • Aggregates - which aggregate parameters from multiple rows and return a single value. • Collations - which describe how to sort some value. Note: For0 码力 | 282 页 | 1.02 MB | 1 年前3
peewee Documentation
Release 3.3.0Person instead of People. This is a convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable using a relational databases, if we were to do a join from Person to Pet then every person with multiple pets would be repeated, once for each pet. It would look like this: query = (Person .select(Person include wildcards here: query = Facility.select().where(Facility.name ** '%tennis%') Matching against multiple possible values How can you retrieve the details of facilities with ID 1 and 5? Try to do it without0 码力 | 280 页 | 1.02 MB | 1 年前3
peewee Documentation Release 3.0.0existing records Atomic updates Deleting records Selecting a single record Create or get Selecting multiple records Filtering records Sorting records Getting random records Paginating records Counting records Person instead of People. This is a convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable using a relational databases, if we were to do a join from Person to Pet then every person with multiple pets would be repeated, once for each pet. It would look like this: query = (Person0 码力 | 319 页 | 361.50 KB | 1 年前3
peewee Documentation Release 3.1.0existing records Atomic updates Deleting records Selecting a single record Create or get Selecting multiple records Filtering records Sorting records Getting random records Paginating records Counting records Person instead of People. This is a convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable using a relational databases, if we were to do a join from Person to Pet then every person with multiple pets would be repeated, once for each pet. It would look like this: query = (Person0 码力 | 332 页 | 370.77 KB | 1 年前3
peewee Documentation Release 2.10.2Databases Adding Request Hooks Additional connection initialization Advanced Connection Management Using multiple databases Database Errors Automatic Reconnect Logging queries Generating skeleton code Adding a existing records Atomic updates Deleting records Selecting a single record Create or get Selecting multiple records Filtering records Sorting records Getting random records Paginating records Counting records Person instead of People. This is a convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable0 码力 | 275 页 | 276.96 KB | 1 年前3
共 16 条
- 1
- 2













