Fix N+1 Query in Vets Endpoint-created-by-agentic

[shaykeren]

Description

This PR addresses the N+1 query performance issue in the /vets.html endpoint by implementing the following changes:

1. Changed FetchType.EAGER to FetchType.LAZY in the Vet entity
2. Added @NamedEntityGraph to optimize loading of specialties
3. Added necessary database indexes on vet_specialties.vet_id and specialties.id

Changes Made

1. Modified Vet.java:

   • Changed fetch type to LAZY
   • Added NamedEntityGraph for specialties

2. Added new database indexes in indexes.sql:

   • Created index on vet_specialties(vet_id)
   • Created index on specialties(id)

Testing

The changes have been tested locally and show significant improvement in query performance by reducing the number of database queries executed when loading vets and their specialties.

Related Issues

Fixes #83

Expected Outcome

• Reduced number of database queries when loading vets and their specialties
• Improved response time for the /vets.html endpoint
• Better overall application performance