Skip to content

Issue 52417: StackOverflowError analyzing queries with linked core schema#6386

Merged
labkey-jeckels merged 3 commits intodevelopfrom
fb_52417_linkedSchemaStackOverflow
Feb 28, 2025
Merged

Issue 52417: StackOverflowError analyzing queries with linked core schema#6386
labkey-jeckels merged 3 commits intodevelopfrom
fb_52417_linkedSchemaStackOverflow

Conversation

@labkey-jeckels
Copy link
Contributor

Rationale

We can break a recursion cycle when checking linked schema FKs.

Changes

  • Use the SchemaKey from the schema without creating the full TableInfo
  • Scope the dependency error info to the dependency analysis

@NotNull
String getSchemaName();

default SchemaKey getSchemaPath()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UserSchema already has getPath(), we should probably use that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad it has both getPath() and getSchemaPath(). That doesn't seem like a good idea.

@labkey-jeckels labkey-jeckels merged commit 97461c4 into develop Feb 28, 2025
4 checks passed
@labkey-jeckels labkey-jeckels deleted the fb_52417_linkedSchemaStackOverflow branch February 28, 2025 00:00
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.

2 participants