Comma join on values without any aliases results in variable not found warnings

[alancai98]

Description

• Comma joining two values in a from source without any alias results in variable not found warnings from the planner

To Reproduce

Steps to reproduce the behavior:

PartiQL Shell
Version: 1.1.0-742e1501c
partiql ▶ SELECT * FROM <<{'a': 1}>>, <<{'a': 2}>>;
w: [semantic] Variable reference (_0) could not be found in the database environment or in the set of available locals. Locals: [_0].
w: [semantic] Expression always returns missing
w: [semantic] Variable reference (_0) could not be found in the database environment or in the set of available locals. Locals: [_0].
w: [semantic] Variable reference (_0) could not be found in the database environment or in the set of available locals. Locals: [_0].
w: [semantic] Variable reference (_0) could not be found in the database environment or in the set of available locals. Locals: [_0].
w: [semantic] Expression always returns missing
w: [semantic] Variable reference (_0) could not be found in the database environment or in the set of available locals. Locals: [_0].
w: [semantic] Variable reference (_0) could not be found in the database environment or in the set of available locals. Locals: [_0].

=== RESULT ===
<<
  {}
>>

Expected Behavior

When doing a normal explicit CROSS JOIN or providing an alias to one or more values, it works as expected

Using a CROSS JOIN

partiql ▶ SELECT * FROM <<{'a': 1}>> CROSS JOIN <<{'a': 2}>>;

=== RESULT ===
<<
  {
    a: 1,
    a: 2
  }
>>

OK!

Providing an alias to the comma-join values:

partiql ▶ SELECT * FROM <<{'a': 1}>> AS t1, <<{'a': 2}>> AS t2;

=== RESULT ===
<<
  {
    a: 1,
    a: 2
  }
>>

Additional Context

• Java version: 17
• PartiQL version: 1.1.0-742e1501c
• Add any other context about the problem here.
  • Pre-1.0 CLIs do not exhibit this behavior.