Source date save now checks before using TRANSLATE scalar
#1175
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
Signed-off-by: Liam Allan <mrliamallan@live.co.uk>
worksofliam
changed the title
TRANSLATE scalar
chrjorgensen
requested changes
Mar 26, 2023
Signed-off-by: Liam Allan <mrliamallan@live.co.uk>
|
@chrjorgensen Added the fix you suggested! Please retest whenever you have a moment :) |
Signed-off-by: Liam Allan <mrliamallan@live.co.uk>
Signed-off-by: Liam Allan <mrliamallan@live.co.uk>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
SQL
TRANSLATEis expensive when inserting a lot of data. This was very visible when working with large files. Translate is only required for source colour support, so therefore the save should only use translate when source colour is enabled.I don't use source colours and this has sped up the save process significantly.
Checklist
console.logs I added