Skip to content

This commit fixes a database error in the `ingest_references_backgrou…

Edouard Legoupil requested to merge feature-deduplicate-and-find-references into main_dev

Created by: Edouard-Legoupil

…ndfunction inbackend/api/knowledge.py`.

The function was attempting to fetch references using a knowledge_card_id column on the knowledge_card_references table, which does not exist. This caused a sqlalchemy.exc.DatabaseError because of the incorrect column name.

The SQL query has been corrected to properly join knowledge_card_references with the knowledge_card_to_references table to retrieve the correct references based on the knowledge_card_id. This resolves the traceback and allows the background ingestion task to function as intended.

  • 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