easy version control. • Versatility: Integrate with various documentation platforms and support multiple output formats. • Open-Source & Community Support: Backed by a [strong community](https://forum 13.2 Define multiple addresses 13 NETWORK DIAGRAM (NWDIAG) db01; db02; } } @enduml 13.2 Define multiple addresses @startuml nwdiag { network dmz { address = "210.x.x.x/24" // set multiple addresses (using include nwdiag { network dmz { address = "210.x.x.x/24" // set multiple addresses (using comma) web01 [address = "210.x.x.1, 210.x.x.20", description = "<$application_server>\n

= "172.x.x.2"]; db01; db02; } } @enduml 13.2 Define multiple addresses @startuml nwdiag { network dmz { address = "210.x.x.x/24" // set multiple addresses (using comma) web01 [address = "210.x.x.1, include nwdiag { network dmz { address = "210.x.x.x/24" // set multiple addresses (using comma) web01 [address = "210.x.x.1, 210.x.x.20", description = "<$application_server>\n db01; } network dmz { address = "210.x.x.x/24" user [description = "<&person*4.5>\n user1"]; // set multiple addresses (using comma) web01 [address = "210.x.x.1, 210.x.x.20", description = "<&cog*4>\nweb01"]

= "172.x.x.2"]; db01; db02; } } @enduml 12.2 Define multiple addresses @startuml nwdiag { network dmz { address = "210.x.x.x/24" // set multiple addresses (using comma) web01 [address = "210.x.x.1, include nwdiag { network dmz { address = "210.x.x.x/24" // set multiple addresses (using comma) web01 [address = "210.x.x.1, 210.x.x.20", description = "<$application_server>\n db01; } network dmz { address = "210.x.x.x/24" user [description = "<&person*4.5>\n user1"]; // set multiple addresses (using comma) web01 [address = "210.x.x.1, 210.x.x.20", description = "<&cog*4>\nweb01"]

= "172.x.x.2"]; db01; db02; } } @enduml 13.2 Define multiple addresses @startuml nwdiag { network dmz { address = "210.x.x.x/24" // set multiple addresses (using comma) web01 [address = "210.x.x.1, include nwdiag { network dmz { address = "210.x.x.x/24" // set multiple addresses (using comma) web01 [address = "210.x.x.1, 210.x.x.20", description = "<$application_server>\n db01; } network dmz { address = "210.x.x.x/24" user [description = "<&person*4.5>\n user1"]; // set multiple addresses (using comma) web01 [address = "210.x.x.1, 210.x.x.20", description = "<&cog*4>\nweb01"]

Zeile oder Aggregation. Sollte mehr zurückgegeben werden, wird es zu einem Laufzeitfehler kommen (“Multiple rows in a singleton select…”).  Obwohl es einen echten Fehler berichtet, kann die Nachricht etwas Versuche, ein UPDATE … RETURNING … auszuführen, das mehrere Zeilen betrifft, führen zu dem Fehler “multiple rows in singleton select”. Wenn die Anweisung keine Datensätze aktualisiert, enthalten RETURNING-Klausel vorhanden ist und mehr als ein übereinstimmender Datensatz gefunden wird, wird ein Fehler “multiple rows in singleton select” ausgegeben. Dieses Verhalten kann sich in einer späteren Version von

lasts 10 days [Task2] on {Bob:50%} lasts 2 days then [Task3] on {Alice:25%} lasts 1 days @endgantt Multiple resources can be assigned to a task: @startgantt [Task1] on {Alice} {Bob} lasts 20 days PlantUML replaced by return !function – !definelong should be replaced by !procedure. • !include now allows multiple inclusions : you don't have to use !include_many anymore • !include now accepts a URL, so you don't Notice that this library requires an ma_ prefix on sprites names, this is to avoid clash of names if multiple sprites have the same name on different libraries. You may also include the common.puml file, eg:

lasts 10 days [Task2] on {Bob:50%} lasts 2 days then [Task3] on {Alice:25%} lasts 1 days @endgantt Multiple resources can be assigned to a task: @startgantt [Task1] on {Alice} {Bob} lasts 20 days PlantUML replaced by return !function – !definelong should be replaced by !procedure. • !include now allows multiple inclusions : you don't have to use !include_many anymore • !include now accepts a URL, so you don't Notice that this library requires an ma_ prefix on sprites names, this is to avoid clash of names if multiple sprites have the same name on different libraries. You may also include the common.puml file, eg:

define and !definelong anymore. Use !function and variable definition instead • !include allows now multiple inclusions : you don't have to use !include_many anymore • !include now accept URL, so you don't Notice that this library requires an ma_ preffix on sprites names, this is to avoid clash of names if multiple sprites have the same name on different libraries. You may also include the common.puml file, eg:

replaced by return function and !definelong should be replaced by void function. • !include now allows multiple inclusions : you don't have to use !include_many anymore • !include now accepts a URL, so you don't Notice that this library requires an ma_ prefix on sprites names, this is to avoid clash of names if multiple sprites have the same name on different libraries. You may also include the common.puml file, eg:

Notice that this library requires an ma_ preffix on sprites names, this is to avoid clash of names if multiple sprites have the same name on different libraries. You may also include the common.puml file, eg: