Cory Grinstead

I don't think there would need to be any functional changes, but on further inspection, i think it may be easier to do the rename after https://github.com/GlareDB/glaredb/issues/2744. That should put...

So this query dives really deep into the pg catalog, and has a ton of tables and exprs that we currently don't support ### Tables - [pg_attrdef](https://www.postgresql.org/docs/current/catalog-pg-attrdef.html) - [pg_sequence](https://www.postgresql.org/docs/current/view-pg-sequences.html) ###...

marking this as `on hold` until we have a strategy for how to handle `json_build_object`.

related to https://github.com/GlareDB/glaredb/issues/1791

@scsmithr Can you make a reproducible example? What shell are you using? We have CTRL+c [configured](https://github.com/GlareDB/glaredb/blob/388a5972ce2105cdb05a25fd5b2c9429a4ff8745/crates/glaredb/src/local.rs#L166) as you described. Only CTRL+d exits the program.ÏÏ

@tychoish we already support this. ```sql create table list_type (v1 double[]); select v1::float[] from list_type; ```

FWIW, deltalake does support `RENAME COLUMN` and it's even in the [official implementation](https://docs.delta.io/latest/delta-batch.html#rename-columns), but it doesn't look like it's made it's way into delta-rs yet. It's currently marked as _experimental_,...

I think we'd also want to expose a function for creating the lists directly instead of casting. we have ways of doing this for lists. ```sql # the array literal...

reclassifying as "feature" as it's technically not a bug, but just missing functionality.

> Is there a way to use make_list (or array) for both but have the size be optional, like the make function in go? Not very easily. The `make_list` function...