Skip to content

Conversation

@rv2931
Copy link
Collaborator

@rv2931 rv2931 commented Dec 11, 2024

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

@rv2931 rv2931 requested review from SebM42 and njouanin December 11, 2024 11:06
@rv2931 rv2931 changed the title fix: #315 avoid request when no vessel_id found (no excursion, no segment) fix: #345 avoid request when no vessel_id found (no excursion, no segment) Dec 11, 2024
@rv2931 rv2931 force-pushed the 345_error_tastk_create_update_excursion_segments_after_db_clean branch from 07f2424 to fe03e24 Compare December 12, 2024 09:33
@rv2931 rv2931 force-pushed the 345_error_tastk_create_update_excursion_segments_after_db_clean branch from fe03e24 to 82d06fb Compare December 23, 2024 18:01
@rv2931 rv2931 force-pushed the 345_error_tastk_create_update_excursion_segments_after_db_clean branch from 82d06fb to ec5c22a Compare January 5, 2025 21:24
@rv2931 rv2931 force-pushed the 345_error_tastk_create_update_excursion_segments_after_db_clean branch from ec5c22a to d2a91a5 Compare January 8, 2025 00:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BACKEND] Error on task create_update_excursions_segments after db clean

2 participants