fix: #345 avoid request when no vessel_id found (no excursion, no segment) #346
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
rv2931
changed the title
rv2931
force-pushed
the
345_error_tastk_create_update_excursion_segments_after_db_clean
branch
from
07f2424 to
fe03e24
Compare
rv2931
force-pushed
the
345_error_tastk_create_update_excursion_segments_after_db_clean
branch
from
fe03e24 to
82d06fb
Compare
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.
fix #345
Je propose ce contournement pour éviter d'exécuter la requête 'ids in ()' qui cause une erreor dès lors qu'il n'y a aucun vessel trouvé car aucun excursion ou segment après un clean de le DB
A valider