:wave: Hey fellow Gliders! :mechanical_arm: Glide just got even more powerful by introducing the QUERY column! No more complex, multi-column setup to achieve conditional relations. The Query column can: :backhand_index_pointing_right: Filter :backhand_index_pointing_right: Sort AND …

[image] Darren_Murphy: This is a common pattern in computing. As soon as you find a match, exit the loop and move on. Phrasing it like you did makes so much more sense to me. I never saw a single Relation as an iterative loop but rather as a vertical scan. Perhaps these are the same but loop …

[image] nathanaelb: I might still use a self-relation to determine the unique rows of a table (along a given column). For instance if name has a, b, c, a, b, c, then the output on the first three rows would be a, b, c (self-relation with single match, lookup.RowID, if-the-else where lookup.RowID…

@MattLB @Robert_Petitto This sounds interesting… Could you elaborate? Sounds like something which could be super useful for building reports In general without having to add many columns or tables.

I agree, Query is practical for cohort analysis, i.e. reports. With Relation, reporting requires a Template column, a self multiple Relation and a Rollup. With Query, reporting requires a Query and a Rollup. Query is much easier to understand than Template + self Relation.

If you need to create a traditional Relation from a query, you can always using Single Value to pull in the first queried item’s row ID, then create a relation using that. Not hard to figure out but just a tip I came across.

[image] Cameraville: you can always using Single Value to pull in the first queried item’s row ID, then create a relation using that. Not hard to figure out but just a tip I came across. Actually, single value → Whole row would accomplish this in one step. [image] Mast…

Does the query column use updates? Know queries to big tables do and am curious if this works at all in the same way. Thanks so much for your help!

It shouldn’t. It’s just another type of computed column, like a relation.

Haven’t tested this extensively, but having a sort option in query, combined with the sort option in a component allows for secondary sorting. So you can achieve this: Apple 1 oz Apple 2 oz Banana 1 oz Banana 3 oz etc.

[image] BLA_68: combined with the sort option in a component Actually, I think the sorting in the component would override the sorting in the query.

🧲 The QUERY Column: One Column to Rule Them All!

Ask for Help

Robert_Petitto May 15, 2023, 12:06pm 32

Actually, single value → Whole row would accomplish this in one step.

Topic		Replies	Views
🆕 Query column! Community Resources	21	1198	May 5, 2023
👨‍👩‍👧‍👧 Grouping and Sorting TIPS and TRICKS Community Resources tutorial	41	2016	July 12, 2023
App Performance (>10k row apps) Ask for Help	32	1716	June 26, 2022
Multi Filters using Relations: a new way 💡 Ask for Help	29	3651	May 6, 2025
To relate, or not to relate, that's the question Ask for Help	11	832	August 2, 2022

🧲 The QUERY Column: One Column to Rule Them All!

Related topics