You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm facing performance issues in Supabase, where foreign keys are not automatically indexed. This causes some queries to be inefficient, particularly when working with large datasets. Supabase's performance editor highlights this as a key optimization concern, and I have to manually create indexes for foreign keys, which is not ideal for scalability or developer experience.
Solution
I would like Raiden to automatically create indexes on foreign key columns when models are applied to Supabase. This feature should ensure that whenever a foreign key is added, the corresponding index is automatically generated, improving query performance without manual intervention.
The text was updated successfully, but these errors were encountered:
@vani-rf It seems the feature is able to generate the model, but after updating the tag, it still tries to generate the same tag (see screenshot). It looks like this needs to be revisited, especially the part that compares the differences—because there is no difference here, yet it keeps showing as if there is.
Problem
I'm facing performance issues in Supabase, where foreign keys are not automatically indexed. This causes some queries to be inefficient, particularly when working with large datasets. Supabase's performance editor highlights this as a key optimization concern, and I have to manually create indexes for foreign keys, which is not ideal for scalability or developer experience.
Solution
I would like Raiden to automatically create indexes on foreign key columns when models are applied to Supabase. This feature should ensure that whenever a foreign key is added, the corresponding index is automatically generated, improving query performance without manual intervention.
The text was updated successfully, but these errors were encountered: