Skip to content

SQLSelect — AddHaving passes wrong argument order #64

Description

@Ben-Gonzalez-97

SQLSelect: correct AddHaving argument order

  • Component: src/ClassModules/SQLSelect.cls (around 71–95)

Problem

  • Calls SQLCondition.Create with (Field, op, Value) but signature is (Expression1, Expression2, Operator).

Snippet (actual)

NewHaving.Create Field, op, Value

Expected

NewHaving.Create Field, Value, op

Steps to Reproduce

  1. Add a HAVING with a non-default operator.

Actual

  • Generates the comparison with swapped operands/operator.

Proposed Fix

  • Pass (Field, Value, op) consistently in both branches.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions