SQLSelect — LeftJoin/RightJoin ByRef type mismatch

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
sql
Domain
databases

Research direction

Open src/ClassModules/SQLSelect.cls around lines 120–143 and inspect the LeftJoin and RightJoin declarations and their calls to AddJoin. Compile or reproduce the strict-compilation case using string literals; done means both methods compile without the ByRef argument type mismatch.

Written by the indexing model from the issue text.

Description

SQLSelect: type LeftJoin/RightJoin params as String

  • Component: src/ClassModules/SQLSelect.cls (around 120–143)
Problem
  • Untyped parameters (Variant ByRef) cause mismatches when passed into AddJoin.
Snippet (actual)
Public Sub LeftJoin(sTable, sAlias, Optional sCondition As String = "")
    AddJoin "LEFT OUTER", sTable, sAlias, sCondition
End Sub

Public Sub RightJoin(sTable, sAlias, Optional sCondition As String = "")
    AddJoin "RIGHT OUTER", sTable, sAlias, sCondition
End Sub
Expected
Public Sub LeftJoin(sTable As String, sAlias As String, Optional sCondition As String = "")
    AddJoin "LEFT OUTER", sTable, sAlias, sCondition
End Sub

Public Sub RightJoin(sTable As String, sAlias As String, Optional sCondition As String = "")
    AddJoin "RIGHT OUTER", sTable, sAlias, sCondition
End Sub
Steps to Reproduce
  1. Call LeftJoin/RightJoin with string literals under strict compilation.
Actual
  • Compile-time "ByRef argument type mismatch" in some contexts.
Proposed Fix
  • Type parameters as String.

Dominant language
VBA
Stars
90
Forks
18
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Beakerboy/VBA-SQL-Library

All issues in Beakerboy/VBA-SQL-Library

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.