-
Notifications
You must be signed in to change notification settings - Fork 34
Adding regex support for (sub)commands #116
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
Open
david-kn
wants to merge
2
commits into
nautobot:develop
Choose a base branch
from
david-kn:feat_command_regex_support
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm definitely a bit concerned about potential performance impact of this design. It should be possible to do this as an actual DB query, rather than querying for
all()and then iterating through the results, though from some quick Googling it looks like custom SQL might be needed to make that possible...Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HI Matthew, thanks for your response and I understand this concern and agree with it.
I'm not familiar with with your code base and didn't want to dig to deep to explore (and reinvent the wheel) the best possible way to interconnect your Django with queries / SQL queries. I rather wanted to kick off this initiative and show that however this might be not that elegant, the update wouldn't have to be extensive to add this neat feature.
Probably some
.raw()method to run directly SQL query could help with this (?) as I don't think that django libs would allow such a query. On the other hand, don't you mind writing and mixing SQL queries into your otherwise python code?On the other hand, amount of these records should be always very limited so the performance should have not been really impacted? But I totally understand and agree that this (performance) aspect as well as conceptual perspective should be always considered and questioned.
I'd leave the final approach to you as your team is in owner/maintainer role :-)