Tracking: struct (aka row or record) DataType Support

[xiangjinwu]

• TEXT format output: Different display format for array/struct with pg #4769
• TEXT format input: expr: string to struct cast #7369
• BINARY format: bug(frontend): pgwire binary response unimplemented for list and struct #7949
• type oid: feat: obtain custom struct's attribute information from oid like postgres #9434
• (st).* expanding to multiple columns bug: array of struct #6934
• Tracking(sink datatype mapping): Type missing when sink to MySQL, PostgreSQL or TiDB #9603
• Support CREATE TYPE
• PG-incompatibility: IS NULL of all-null row/struct #10150
• feat(binder): enhance support of struct.* (and table.*) #10847
• Support altering fields of struct-type column #19755

Tests:

• test: enable struct duckdb test cases #6556
• sqlsmith: Generate struct and list exprs #7132
• RandValue: impl RandValue for list / struct / jsonb #8001

Also acknowledging some facts:

• The type syntax struct<fieldA typeA, fieldB typeB> does not exist in PostgreSQL.
• Casting between 2 struct types matches fields of both sides by position rather than name. This is disallowed by PostgreSQL, but consistent with DuckDB (until 0.9.0) and Flink.
  • DuckDB: with t(v) as (select row(3.2, true)::struct(x decimal, y boolean)) select v::struct(a int, b int) from t;
  • Flink: with t(v) as (select cast(row(3.2, true) as row<x decimal, y boolean>)) select cast(v as row<a int, b int>) from t;

[github-actions]

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄