and >>. You can also define notes using note left of , note right of , note top of , note bottom of key- words. You can also define a note on the last defined class using note left, note right, note top 108 / 550 5.9 Partition 5 ACTIVITY DIAGRAM (LEGACY) note right: This action has to be defined "Some action" --> (*) note left This note is on several lines end note @enduml 5.9 Partition You can define define a partition using the partition keyword, and optionally declare a background color for your partition (Using a html color code or name) When you declare activities, they are automatically put in the

107 / 551 5.9 Partition 5 ACTIVITY DIAGRAM (LEGACY) note right: This action has to be defined "Some action" --> (*) note left This note is on several lines end note @enduml 5.9 Partition You can define define a partition using the partition keyword, and optionally declare a background color for your partition (Using a html color code or name) When you declare activities, they are automatically put in the the last used partition. You can close the partition definition using a closing bracket }. @startuml partition Conductor { (*) --> "Climbs on Platform" --> === S1 === --> Bows } partition Audience #LightSkyBlue

lines end note @enduml 5.9 Partition Vous pouvez définir une partition en utilisant le mot clé partition, et optionnellement déclarer un fond de couleur pour votre partition (En utilisant un code couleur automatiquement mis dans la dernière partition utilisée. Vous pouvez fermer la partition de définition en utilisant les crochets fermants }. @startuml partition Conductor { (*) --> "Climbs on Platform" === S1 === --> Bows } partition Audience #LightSkyBlue { === S1 === --> Applauds } partition Conductor { Bows --> === S2 === --> WavesArmes Applauds --> === S2 === } partition Orchestra #CCCCEE { WavesArmes

Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying Creating a new record Bulk inserts Updating existing records Atomic updates backend Postgresql Extensions DataSet Django Integration Fields Generic foreign keys Hybrid Attributes Key/Value Store Shortcuts Signal support pwiz, a model generator Schema Migrations Reflection Database relationships between models using foreign keys (wikipedia) [http://en.wikipedia.org/wiki/Foreign_key]. This is easy to do with peewee: class Pet(Model): owner = ForeignKeyField(Person, related_name='pets')

our data. This will create the tables with the appropriate columns, indexes, sequences, and foreign key constraints: >>> db.create_tables([Person, Pet]) 1.2.2 Storing data Let’s begin by populating the Message model stores the text content of the tweet, when it was created, and who posted it (foreign key to User). If you like UML, these are the tables and relationships: In order to create these models ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users messages will be accessible # as a special attribute, User.message_set

Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying Creating a new record Bulk inserts Updating existing records Atomic updates sqlite driver Sqlcipher backend Postgresql Extensions MySQL Extensions DataSet Fields Hybrid Attributes Key/Value Store Shortcuts Signal support pwiz, a model generator Schema Migrations Reflection Database having to worry. Things get interesting when we set up relationships between models using foreign key relationships. This is simple with peewee: class Pet(Model): owner = ForeignKeyField(Person, backref='pets')

having to worry. Things get interesting when we set up relationships between models using foreign key relationships. This is simple with peewee: class Pet(Model): owner = ForeignKeyField(Person, backref='pets') our data. This will create the tables with the appropriate columns, indexes, sequences, and foreign key constraints: db.create_tables([Person, Pet]) 1.2.2 Storing data Let’s begin by populating the database Message model stores the text content of the tweet, when it was created, and who posted it (foreign key to User). If you like UML, these are the tables and relationships: In order to create these models

Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying Creating a new record Bulk inserts Updating existing records Atomic updates relationships between models using foreign keys (wikipedia) [http://en.wikipedia.org/wiki/Foreign_key]. This is easy to do with peewee: class Pet(Model): owner = ForeignKeyField(Person, backref='pets') our data. This will create the tables with the appropriate columns, indexes, sequences, and foreign key constraints: db.create_tables([Person, Pet]) Storing data Let’s begin by populating the database

Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying Creating a new record Bulk inserts Updating existing records Atomic updates sqlite driver Sqlcipher backend Postgresql Extensions MySQL Extensions DataSet Fields Hybrid Attributes Key/Value Store Shortcuts Signal support pwiz, a model generator Schema Migrations Reflection Database relationships between models using foreign keys (wikipedia) [http://en.wikipedia.org/wiki/Foreign_key]. This is easy to do with peewee: class Pet(Model): owner = ForeignKeyField(Person, backref='pets')

our data. This will create the tables with the appropriate columns, indexes, sequences, and foreign key constraints: db.create_tables([Person, Pet]) 1.2.2 Storing data Let’s begin by populating the database Message model stores the text content of the tweet, when it was created, and who posted it (foreign key to User). If you like UML, these are the tables and relationships: 12 Chapter 1. Contents: peewee ) # a dead simple one-to-many relationship: one user has 0..n messages, exposed by # the foreign key. because we didn't specify, a users messages will be accessible # as a special attribute, User.messages