What happens?

Consider the case where there are multiple schemas with the same matching score for a Catalog error.

create schema a;
create schema b;
create table a.foo(name text);
create table b.foo(name text);
select * from foo;

Catalog Error: Table with name foo does not exist!
Did you mean "b.foo"?
LINE 1: select * from foo;

There is an equally qualified match in schema a, but Catalog Error just presents the last match.

Here is the relevant snippet of code.

I'd suggest that the code should be changed to present all suggestions that have the same score so that the a user that has tables in multiple schemas with the same name can make the appropriate choice.

Thanks,

Rusty

To Reproduce

create schema a;
create schema b;
create table a.foo(name text);
create table b.foo(name text);
select * from foo;

OS:

Mac OS X

DuckDB Version:

1.0.0

DuckDB Client:

CLI

Full Name:

Rusty Conover

Affiliation:

self

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