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}]}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 trace the SQL projection and
expandexecution paths, locate how aliases are assigned to result properties, then reproduce the behavior with the relevant test suite or a focused temporary check. I’ll implement the smallest general fix, run affected tests, inspect the diff, and submit only after verification. - Assistant
The bug is in the planner transformation:
SELECT expand(...)is rewritten to project the expand argument, and the alias is discarded beforeExpandStepruns.ExpandStepalso hard-codes"value"for scalar elements. I’ll preserve the explicit alias as planner metadata and use it only for scalar expansion, retaining the existing"value"default when no alias was supplied and leaving expanded records/maps unchanged. - Assistant
The first edit command could not run because this environment lacks
python3; no files were changed. I’ll apply the same targeted edits with the available shell tooling and then compile/test. - Assistant
The code changes are in place and the diff is clean. Maven’s wrapper failed before build because
HOMEis unset in this shell, so I’ll rerun with a temporaryHOMEvalue; this is an environment issue, not a test failure. - Assistant
The focused runtime check now returns four rows with property names
[test]and values1..4, confirming the reported case is fixed. The existingExpandParseTestandExpandStepTestalso pass, and the compatibility constructor preserves directExpandStepcallers and the no-alias"value"behavior. I’ll do a final formatting/diff review and then submit.
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
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →