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

decide how to handle not displayed fields (on save) #3

Open
benzkji opened this issue Dec 2, 2016 · 1 comment
Open

decide how to handle not displayed fields (on save) #3

benzkji opened this issue Dec 2, 2016 · 1 comment
Labels

Comments

@benzkji
Copy link
Member

benzkji commented Dec 2, 2016

as for example foreign keys can become invalid, when never visible?

@benzkji benzkji changed the title decide how to handle not displayed fields decide how to handle not displayed fields (on save) Dec 2, 2016
@benzkji
Copy link
Member Author

benzkji commented Nov 14, 2019

one solution: null all (nullable) fields that are not in the current stash. needs to be configurable per field.

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

1 participant