Skip to content

fix: Correct SQL query in reingest_knowledge_card_reference

Edouard Legoupil requested to merge fix-reingest-query-issue into main_dev

Created by: Edouard-Legoupil

The original query was causing a DatabaseError because it was attempting to select knowledge_card_id from the knowledge_card_references table, where the column does not exist.

This commit fixes the issue by modifying the query to join knowledge_card_references with the knowledge_card_to_references table to correctly validate the association between the knowledge card and the reference.

  • Does my code meet the quality standards for releasing packages?
  • Does the reviewer have all the information to validate the features/issues without too much research?
  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports