Skip to content

[Feature]: Database Impact Analysis #1

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

Closed
garrmark opened this issue Apr 2, 2025 · 1 comment
Closed

[Feature]: Database Impact Analysis #1

garrmark opened this issue Apr 2, 2025 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@garrmark
Copy link
Collaborator

garrmark commented Apr 2, 2025

Is your feature request related to a problem?

The CodeLogic knowledge graph contains information about how changes in code will effect database entities and vice versa. Use the this context when code changes are proposed to methods and/or classes that reference database entities.

Describe the solution you'd like

Create an MCP tool that determines the affected column/table/view and then searches for those via the CodeLogic API's

  • /ai-retrieval/search/column
  • /ai-retrieval/search/table
  • /ai-retrieval/search/view

Once these entities are located, use them to get impact analysis data via the API

  • /dependency/impact/full/{id}/list

Augment the user's prompt with this data.

Describe alternatives you've considered

No response

Additional context

No response

Priority

Important

@garrmark garrmark added the enhancement New feature or request label Apr 2, 2025
@garrmark garrmark self-assigned this Apr 2, 2025
@garrmark
Copy link
Collaborator Author

garrmark commented Apr 8, 2025

There is a new tool called codelogic-database-impact that will provide the db impact analysis to the MCP client, the old tool has been renamed codelogic-method-impact

@garrmark garrmark closed this as completed Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant