Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deal with compound/composite keys #1562

Open
eemmiillyy opened this issue Aug 27, 2024 · 0 comments
Open

Deal with compound/composite keys #1562

eemmiillyy opened this issue Aug 27, 2024 · 0 comments

Comments

@eemmiillyy
Copy link
Contributor

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

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

No branches or pull requests

1 participant