this would be useful for me
Why not just use the Lookup by Values block? It uses the same amount of compute to lookup a single column as it does to lookup all columns from a given row.
Or are you just looking for a ‘generic’ version of lookup by values, where the db/cols can be inputted on-the-fly rather than being validated within the flow editor? It doesn’t make any sense (to me) to make that generic version only as a random variant that can only lookup one column.
in my db i store columns like “member-logs-webhook” and “server-logs-webhook”, and when i want to update the webhook, i want to delete the old one, so i want to find the specific use case webhook type, like “(variable)-logs-webhook”
If I understand this correctly, you’re looking for more dynamic versions of the existing blocks, where you can use variables to input database/column names everywhere. Suggesting new different blocks is sort of a strange way to go about that.
If implemented as you request, this will be confusing to end-users because extremely similar but subtly different blocks will exist for the different quirks of what you’re trying to do.
I’d suggest using local variables and conditionals to use 2 different lookups, more dynamic DB lookups may be added in the future but it isn’t a priority.
