ensure all virtual columns are added in inserts and updates #172
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.
If a parent Parent has many Child and Child does not have any
inverse relationship, the FK of Child it's not saved, even though
it is a virtual column. That's why only virtual columns for explicit
relationships were being added during the code generation step.
This, however, has changed so all of the virtual columns of a record
are added in inserts and updates (only once, of course).
Therefore, now relationships with no inverse relationships at all
can be used.
This fixes one of the bugs reported in #170