We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
find_composite_key_candidates just returns one composite key candidate now. That's good for performance.
find_composite_key_candidates
We should also let the user figure out all possible candidate keys as well. That way they can select if they want to.
The text was updated successfully, but these errors were encountered:
@MrPowers I think @souvik-databricks is already on that -> #31
Sorry, something went wrong.
souvik-databricks
Successfully merging a pull request may close this issue.
find_composite_key_candidates
just returns one composite key candidate now. That's good for performance.We should also let the user figure out all possible candidate keys as well. That way they can select if they want to.
The text was updated successfully, but these errors were encountered: