enovia:mql
Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
| enovia:mql [2022/10/27 07:32] – nicoanto | enovia:mql [2022/10/27 07:35] (Version actuelle) – nicoanto | ||
|---|---|---|---|
| Ligne 5: | Ligne 5: | ||
| Consider we have the following datamodel: | Consider we have the following datamodel: | ||
| {{ : | {{ : | ||
| + | |||
| + | We want to retrieve the Person object linked with the Project Space object through Member relationship for which the Project Role is set to Contributor (Member relationship attribute). | ||
| + | |||
| + | If we apply the "// | ||
| + | |||
| + | Now, consider the following MQL command : | ||
| + | < | ||
| + | |||
| + | The MQL engine gives us only myUser3. | ||
| + | |||
| + | **Rule**: | ||
| + | |||
| + | To perform conditional select when expanding an object, you can include a Where clause criteria in the squarebrackets of select from[ ].to[ ] or to[ ].from[ ] clauses. The relationship or type namepattern is specified first, and then may be followed by the Where clause, the fields delimited by the“|” character. | ||
| + | |||
| + | In the previous example, the starting point of the where clause criteria is the expanded relationship. If you want to perform a where clause on the related object (in the example, the Person objects), you can use the following synthax : | ||
| + | < | ||
| + | |||
| + | |||
enovia/mql.1666855942.txt.gz · Dernière modification : (modification externe)
