Applies to: ✅ Data 360 SQL ✅ Tableau Hyper API
Property Graph Queries (PGQ) let you ask relationship questions about your Data 360 objects in SQL. Instead of joining customers to orders to products again and again, you define those connections once as a graph and then match paths.
For an ecommerce site, the usual questions look like this.
A property graph has three parts.
Define the graph in a WITH clause, then query it with GRAPH_TABLE. The COLUMNS clause turns matched properties into ordinary result columns.
Use PGQ when the question is about a path among records. Use ordinary SQL joins when you need one table’s rows plus a few lookup fields.
The commerce examples in this section use the Individual, Sales Order, Sales Order Product, and Goods Product DMOs. A customer places an order, and the order line item points to the product.
Data 360 supports a subset of the SQL/PGQ standard.
| Feature | Support |
|---|---|
Inline property graph definition, WITH pg AS PROPERTY GRAPH (...) | ✅ Supported |
Persisted property graphs, CREATE PROPERTY GRAPH | ❌ Not supported |
GRAPH_TABLE with MATCH, COLUMNS, and WHERE | ✅ Supported |
ONE ROW PER MATCH and ONE ROW PER STEP | ✅ Supported |
| Multi-hop and quantified paths | ✅ Supported |
| Label expressions (conjunction, disjunction, negation, wildcard) | ✅ Supported |
Fixed and range edge quantifiers, {n} and {m,n} | ✅ Supported |
A quantifier lower bound of 0 (for example, {0,3} or {,2}) | ❌ Not supported yet |
Unbounded quantifiers (for example, {2,}) | ❌ Not supported yet |
The *, +, and ? quantifier forms | ❌ Not supported yet |
| Shortest-path queries | ❌ Not supported yet |
j
