Lotus Garland
Twenty-eight lotus blooms on a cord. Made to order for Lakshmi Pooja and only in season.
Where to buy
Every shop that carries it, cheapest in-stock first.
Price, stock and lead time are properties of the AVAILABLE_AT relationship — the same product costs different amounts at different shops, and that fact belongs to the pairing.Product → AVAILABLE_AT → Florist → LOCATED_IN → Location
| Shop | Area | Rating | Price | Availability |
|---|---|---|---|---|
| Jayanagar Hoovina Angadi | Jayanagar | 4.7(466) | ₹828 | In stock · Same day |
| Madurai Mala Kadai | Meenakshi Nagar | 4.6(288) | ₹918 | In stock · Same day |
| Mylapore Mala Stores | Mylapore | 4.8(638) | ₹972 | In stock · Same day |
| Mysuru Hoo Mandi | Devaraja Mohalla | 4.6(267) | ₹1,044 | In stock · Same day |
4 of 4 shops have it in stock right now.
If you can't get it
Alternatives found by walking the substitution chain up to three hops.
Closeness is multiplied along the chain, so a substitute reached in two hops automatically scores lower than a direct one — no rule had to say so.Product → SUBSTITUTE_FOR*1..3 → Product
Lotus garlands are made to order and seasonal; rose is the standing alternative.
Lotus garlands are made to order and seasonal; rose is the standing alternative.
Needed for
Every occasion that calls for this, and how much each one needs.
Exactly the same relationship as the checklist, traversed in the other direction and at the same cost. A relational schema would need a second index for this.Occasion → NEEDS → Product (read backwards)
- Lakshmi PoojaRecommended1 piece
Made to order and only in season — ask two days ahead.
How Lotus Garland connects to Lakshmi Pooja
The route the graph took, not just the fact that a route exists.
This is the query with no relational equivalent. A join returns rows; the joins that connected them are gone by the time the result exists. Only a graph can hand back the path itself.shortestPath, up to 6 hops
- Lotus Garland is needed by
- Lakshmi Pooja
1 hop through the graph