What happens?

Using .rows in the CLI switches to columns mode (the same behavior as .columns) instead of switching to the default, expected behavior.

To Reproduce

Minimal reproducer (Using a new DuckDB CLI session):

.rows
FROM VALUES (1,2,3), (4,5,6) AS t(a,b,c);

A bit more explanatory of a typical use-case (Using a new DuckDB CLI session):

-- Default behavior (row-wise)
FROM VALUES (1,2,3), (4,5,6) AS t(a,b,c);
-- Observe bug: explicitly set to row-wise (this fails by going to columns instead)
.rows
FROM VALUES (1,2,3), (4,5,6) AS t(a,b,c);
-- Switch to columns (nothing changes) then try to switch back (also doesn't work)
.columns
FROM VALUES (1,2,3), (4,5,6) AS t(a,b,c);
.rows
FROM VALUES (1,2,3), (4,5,6) AS t(a,b,c);

OS:

OSX 15.3 aarch64 and Ubuntu 22.04 x86_64

DuckDB Version:

1.2.0

DuckDB Client:

CLI

Hardware:

No response

Full Name:

Teague Sterling

Affiliation:

23andMe

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?

Not applicable - the reproduction does not require a data set

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