chore(ibis): add function list for DuckDB

[goldmedal]

Description

The following SQL in DuckDB builds the function list:

select 
  distinct function_type, 
  function_name, 
  case when regexp_matches(return_type, '^[A-Z]+\[\]') then 'array' else lower(return_type) end as return_type, 
  array_to_string(parameters, ',') as param_names, 
  array_to_string(
    list_transform(
      parameter_types, 
      t -> case when regexp_matches(t, '^[A-Z]+\[\]') then 'array' else lower(t) end
    ), 
    ','
  ) as param_types, 
  description 
from 
  duckdb_functions() 
where 
  function_type in ('scalar', 'aggregate') 
  and function_name not like '%__internal%' 
  and regexp_matches(function_name, '[_a-zA-Z0-9]+');

• I didn't add a test case to test all functions because there are some issues with generating the testing SQL.
• Currently, some functions miss the description because DuckDB doesn't define it.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[douenergy]

a little bit duckling sql

SELECT
    function_type,
    function_name,
    return_type:     case when return_type.contains('[]') then 'array'
                     else return_type.lower() end,
    parameter_names: parameters.aggregate('string_agg'),
    parameter_types: case when parameter_types.aggregate('string_agg').contains('[]') then 'array'
                     else parameter_types.aggregate('string_agg').lower() end,
    description
    
 FROM duckdb_functions()
 
 WHERE function_type in ('scalar', 'aggregate')
        and function_name not like '%__internal%'
        and function_name.regexp_matches('[_a-zA-Z0-9]+');

[douenergy]

Code looks good , just one small comment

[douenergy]

I think we need a comment explaining where the number 438 comes from.

[douenergy]

Thanks @goldmedal !