Skip to content

Changed behaviour of getvariable #16260

@MPizzotti

Description

@MPizzotti

What happens?

with duckdb versions prior to version 1.1.3, i would run this command for ease of use:
CREATE MACRO _(x) AS getvariable(x);
so that i didn't have to write it each time,
but now on duckdb 1.2.0 i get back this error:
Not implemented Error: getvariable requires a constant input

  1. is this expected?
  2. is there a way to rename it, and in general, to rename functions such as getvariable ?

To Reproduce

for reproducing, try this command on duckdb 1.1.3 and duckdb 1.2.0:
CREATE MACRO _(x) AS getvariable(x);

OS:

any

DuckDB Version:

1.2.0

DuckDB Client:

any

Hardware:

No response

Full Name:

Massimiliano Pizzotti

Affiliation:

EssilorLuxottica

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a stable release

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?

  • Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

  • Yes, I have

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions