Skip to content

iproto: fix schema with constraints fetch #285

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

Merged
merged 2 commits into from
Feb 28, 2023

Conversation

DifferentialOrange
Copy link
Member

Before this patch, only schemas with 3-level nesting were expected. Simple foreign keys schema has 4-level nesting. After this patch, nesting depth up to 32 is supported. (There are no known schemas with such nesting, but this should be enough for any future extensions.)

Closes #282

@DifferentialOrange DifferentialOrange force-pushed the DifferentialOrange/gh-282-schema-depth branch 2 times, most recently from 28f506b to 162ae62 Compare February 27, 2023 11:49
Before this patch, only schemas with 3-level nesting were expected.
Simple foreign keys schema has 4-level nesting. After this patch,
nesting depth up to 32 is supported. (There are no known schemas with
such nesting, but this should be enough for any future extensions.)

Closes #282
@DifferentialOrange DifferentialOrange force-pushed the DifferentialOrange/gh-282-schema-depth branch from 162ae62 to 4b457ea Compare February 27, 2023 12:42
@DifferentialOrange DifferentialOrange marked this pull request as ready for review February 27, 2023 13:47
@DifferentialOrange DifferentialOrange merged commit 56dfa4d into master Feb 28, 2023
@DifferentialOrange DifferentialOrange deleted the DifferentialOrange/gh-282-schema-depth branch February 28, 2023 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Exception on connection to server with foreign_key
2 participants