Fix return type error when running incremental on first time ETL. #2
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.
This PR addresses an issue where running
artisan etls:run <etl-name> --incremental
against an empty database table will silently fail due to a mismatched return type inDbLoader::getIncrementalLastValue
.getIncrementalLastValue
use's Laravel'sBuilder
object to build a query against the configured connection, ultimately returning the result of thevalue
call. This works when the destination database table already has data, because it returns the value of the last row in the configured column. However, when the database table is empty, thevalue
call returnsnull
, which is not whatgetIncrementalLastValue
expects to return. The type is not converted and the extraction fails.