Skip to content

format: generalize current catalog/schema for arbitrarily nested namespaces #4564

Closed as duplicate

Description

@lidavidm

What feature or improvement would you like to see?

In theory, if a vendor supports arbitrarily nested table namespaces (a la Iceberg catalog), then we should be able to USE a nested namespace too, right?

  • Does any vendor actually support this?
  • How should we represent the namespace to the API, considering escaping?

Activity

  1. lidavidm commented on Jul 22, 2026

    @lidavidm
    MemberAuthor

    I wonder if we need an explicit get/set string list function.

    If we want to support this we also need to generalize bulk ingest etc.

  2. lidavidm commented on Jul 22, 2026

    @lidavidm
    MemberAuthor

    #46 and #320 already exist; let's use those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions