Skip to content
This repository was archived by the owner on Mar 26, 2026. It is now read-only.
This repository was archived by the owner on Mar 26, 2026. It is now read-only.

Deal with compound/composite keys #1562

Description

@eemmiillyy

Is your feature request related to a problem? Please describe.

With direct SQL access users will be able to create composite primary keys. This will not work with the SDK. We need to eventually support these cases. This will require an API surface change since alot of our SDK methods are unkeyed and are previously assumed to be an id or xata_id. Since this is unkeyed input and the user may not have either of those fields as primary keys (or at all) we cannot rely on those assumptions anymore.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions