René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[BUG]","articleBody":"**Describe the bug**\nThe `||` string concatenation operator fails when used in a query against a view, but works correctly against a resource. The error returned is:\n```\nquery rewriting for indirection: cannot find col = ''\n```\n\n**To Reproduce**\n\nRun the following against the `homebrew` provider (free, no auth required):\n```sql\nSELECT \n  'homebrew://' || formula_name as formula_uri\nFROM  \n  homebrew.formula.vw_info\nWHERE formula_name = 'stackql';\n```\n\nThe same query pattern works correctly against a resource:\n```sql\nSELECT \n  'homebrew://' || name as formula_uri\nFROM  \n  homebrew.formula.formula\nWHERE formula_name = 'stackql';\n```\n\n**Expected behavior**\n\nBoth queries return a single row with `formula_uri = 'homebrew://stackql'`.\n\n**Additional context**\n\nAssigned to @claude for investigation and fix.\n\n- Fix should be isolated to the query rewriter's indirection/column resolution logic - the bug is that string literal operands on the left side of `||` are not being resolved correctly during view expansion\n- Fix should touch as few files as possible with no refactoring of adjacent logic\n- Add both queries above as robot framework regression tests to the existing homebrew test suite, with the resource query as baseline and the view query as the regression guard","author":{"url":"https://github.com/jeffreyaven","@type":"Person","name":"jeffreyaven"},"datePublished":"2026-03-17T07:56:54.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/623/stackql/issues/623"}