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

Clarify Foreign Keys #24

Open
scott-w opened this issue Nov 14, 2016 · 2 comments
Open

Clarify Foreign Keys #24

scott-w opened this issue Nov 14, 2016 · 2 comments
Labels

Comments

@scott-w
Copy link
Contributor

scott-w commented Nov 14, 2016

In the README, we should clarify how ForeignKey relationships work in the context of SQL Views.

@scott-w scott-w added the docs label Nov 14, 2016
@ktosiek
Copy link
Contributor

ktosiek commented Jan 11, 2017

Does it make sense to use FKs with on_delete different than DO_NOTHING? If not, would a system check for that make sense?

@scott-w
Copy link
Contributor Author

scott-w commented Jan 11, 2017

In theory, I believe you can write SQL that manages the update and delete cases to map them through. It does feel like an edge case, however, so I'd be happy to change the default to models.DO_NOTHING somehow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants