Issue found on page 'Map Functions': element_at, map_extract, and map[entry] return an array

[rpbouman]

The map retrieval functions:

• element_at: https://duckdb.org/docs/sql/functions/map#element_atmap-key
• map_extract: https://duckdb.org/docs/sql/functions/map#map_extractmap-key
• map[entry]: https://duckdb.org/docs/sql/functions/map#mapentry

return an array.
This is described in https://duckdb.org/docs/sql/data_types/map#retrieving-from-maps.

But the description of these functions do not mention that, and the given examples suggesting they return the value directly, not an array containing the value.

Page URL: https://duckdb.org/docs/sql/functions/map.html

[soerenwolfers]

This was changed on HEAD in duckdb/duckdb#14175. The documentation PR at #4201 was merged prematurely.

You can already try it out the new behavior in the nightly build via pip install duckdb --upgrade --pre or via the instructions at https://duckdb.org/docs/installation/?version=main&environment=cli&platform=linux&download_method=direct&architecture=x86_64

@szarnyasg Let me know if you think it's worth reverting and reinstating after 1.2.0 is released.

[rpbouman]

Hi @soerenwolfers , thanks! Ok - I guess I'll close this one then?

(BTW I much prefer MAP extraction methods to not wrap the value in an array.)

[vlulla]

I too stumbled upon this just now! It appears that the Map functions docs page states that the stable version of duckdb 1.1.3 (listed on top right of the docs page) will return a value whereas the cli returns the array with one element. It appears to me that the doc is out of sync with the stable version.