In our current database schema, we have two separate tables: commodity and commodity_whitelist. These tables are interconnected and used to create an intermediary view named validated_commodity_view to facilitate our queries. This setup, while functional, has been identified as a bottleneck in our system, contributing to slower query performances due to the overhead associated with maintaining and querying through the intermediary view.
Objective
The primary goal of this ticket is to merge the commodity and commodity_whitelist tables into a single, efficiently structured table. This consolidation aims to eliminate the need for the validated_commodity_view and, as a result, speed up our query processes by reducing complexity and improving data retrieval times.
Expected Benefits
Performance Improvement: Direct queries against a single table will be faster than querying through an intermediary view, especially as our data volume continues to grow.
Simplified Schema: Having one less view and one less table in our database schema simplifies understanding and maintaining our database.
Scalability: A simplified and more efficient schema lays a better foundation for scaling our application as needed.
Description
In our current database schema, we have two separate tables: commodity and commodity_whitelist. These tables are interconnected and used to create an intermediary view named validated_commodity_view to facilitate our queries. This setup, while functional, has been identified as a bottleneck in our system, contributing to slower query performances due to the overhead associated with maintaining and querying through the intermediary view.
Objective
The primary goal of this ticket is to merge the commodity and commodity_whitelist tables into a single, efficiently structured table. This consolidation aims to eliminate the need for the validated_commodity_view and, as a result, speed up our query processes by reducing complexity and improving data retrieval times.
Expected Benefits