This repository has been archived by the owner on Nov 3, 2023. It is now read-only.
Set default to NULL on copy if nullIfEmpty is set #8365
Closed
Conversation
This file contains 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
|
Shouldn't we use |
|
I thought about that too, but that means an integer field would get '0' as default, which is probably not what you want? |
|
0 seems correct for an INT field IMHO. |
|
But its very likely not what you want in a field, because you want to enter a new value. What happens if a new record is created? Are we using 0 or empty? |
|
We are using |
leofeyer
added a commit
that referenced
this pull request
Jun 15, 2016
|
Fixed in aff8643. |
leofeyer
added a commit
that referenced
this pull request
Jun 16, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I have a date field in my DCA which can be NULL and
doNotCopyenabled. If the record is duplicated, the value currently results in 01.01.1970.