ISSUE DESCRIPTION [SQL] "expand" projection is always named "value" ignoring "AS"…
- User
ISSUE DESCRIPTION
[SQL] "expand" projection is always named "value" ignoring "AS"
ArcadeDB Server v26.5.1 (build b6d08fee549dd5930303b362223869901aab0fac/1778533954349/main)Running on Linux 6.17.0-29-generic - OpenJDK 64-Bit Server VM 25.0.3-eaUsing
expandin a projection, the result-set contains an property namedvalueinspite an alias of the formAS x:SELECT expand([1,2,3,4]) AS testresults in:
{"result":[{"value":1},{"value":2},{"value":3},{"value":4}]}Interface
No new interfaces are introduced.
ADDITIONAL ADVICE
Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use
git checkout <file>to restore the file to its original state. You can also reset all changes in the repository usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto get the changes that need to be submitted.CHECKLIST
Before submitting your solution, please go over the following checklist and make sure you've done everything:
- If an error was reported in the issue description, I have successfully reproduced it.
- If an error was reported in the issue description, I have confirmed that my fix resolves the error.
- I have thought about edge cases and made sure my fix handles them as well.
- I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.
Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!
(Current directory: /arcadedb, current file: none) bash-$
- Assistant
I'll start by exploring the repository structure and locating the code that handles SQL
expandprojections and aliases. - Assistant
Next I'll search the engine for how SQL
expandand projection aliases are implemented. - Assistant
I found the SQL expand step — I'll inspect that and related projection code.
- Assistant
Let me read the rest of ExpandStep.java and the Projection related code for expand and alias.
- Assistant
Found the hard-coded
"value"property — next I'll check how projection aliases flow through expand. - Assistant
Let me look at getExpandContent in ProjectionItem more carefully.
- Assistant
I need to see how projection aliases are chosen when none is given, and how ExpandStep uses the property name.
- Assistant
I'll check for other code paths and whether similar patterns already use the projection alias.
- Assistant
I'll look at unwind and related tests for parallel alias-handling patterns.
- Assistant
I'll verify the bug by running a small reproduction against the project.
- Assistant
Implementing the fix: preserve the expand alias (default
"value") and use that property name in ExpandStep. - Assistant
Let me make the edits.
- Assistant
Updating ExpandStep to use the projection property name for scalar values.
- Assistant
I need to keep the property name available when building scalar expanded results.
- Assistant
Now update the setProperty line and where propName is obtained.
- Assistant
Now I need to set fieldName from propName when reading the aggregate item.
- Assistant
I'll compile the engine and run targeted tests to verify the fix.
- Assistant
HOME is not set. Let me set it.
- Assistant
Compilation succeeded. Next I'll run the expand-related tests and a quick check for the AS alias.
- Assistant
Tests passed. I'll add a temporary script to verify both the AS alias and the default without AS.
- Assistant
I'll remove the temporary test file since new tests shouldn't be added to the repo.
- Assistant
Checking for other ExpandStep construction paths and related edge cases.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →