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

Handle stored logic with parameters in the dependency graph DAT-15747 #5581

Merged
merged 4 commits into from
Feb 20, 2024

Conversation

wwillard7800
Copy link
Contributor

@wwillard7800 wwillard7800 commented Feb 8, 2024

Impact

  • Bug fix (non-breaking change which fixes expected existing functionality)
  • Enhancement/New feature (adds functionality without impacting existing logic)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

This change handles procedures and functions which have parameters. The name of these objects that comes back from the dependency query does not include the actual parameter names, just the types. This makes the dependency sorting ignore these objects and just put them at the bottom of the list, instead of in their correct place.

Things to be aware of

Things to worry about

Additional Context

String name = schemaName + "." + obj.getName();
if (dependencyOrder.contains(name)) {
String objectName = obj.getName();
String name = schemaName + "." + objectName;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice, now we can have the same object in different schemas.

@suryaaki2 suryaaki2 merged commit d5c3ead into master Feb 20, 2024
33 of 34 checks passed
@suryaaki2 suryaaki2 deleted the DAT-15747 branch February 20, 2024 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants