2
Suggestive Schema Indexing
Source: supabase/supabase#6686 · opened by @sandbox-apps
Problem
Thinking about indexing while developing and writing feature is hard. After all we dont know what would be needed to be index when the application grows specially when we are talking about compound index (maybe optimized for sorting)
Suggested solution
Firestore has this kind suggestive indexing.
How does Firestore does this? By introspecting the ran query against the database schema.
I think we can also do this by looking the introspecting indices matching it in the query that being ran.
Then the supabase client will suggest in the console what must be index, or much we can tap a console link or a yes or no that will modify the supabase table to apply the schema.
Additional Context
This is suggested in the frontend code through console.log or print then click the link and will be auto added in the firebase console

Suggested solution
Firestore has this kind suggestive indexing.
How does Firestore does this? By introspecting the ran query against the database schema.
I think we can also do this by looking the introspecting indices matching it in the query that being ran.
Then the supabase client will suggest in the console what must be index, or much we can tap a console link or a yes or no that will modify the supabase table to apply the schema.
Additional Context
This is suggested in the frontend code through console.log or print then click the link and will be auto added in the firebase console
![image](
![image](
No pledges yet. Be the first to back this.
Comments
Similar requests
Default schema for Foreign Keys
1 vote · 0 comments
Add table-specific filtering to the Database Indexing page
2 votes · 0 comments
Allow selecting a schema in database connection string settings
4 votes · 0 comments
Table Editor UX: unclear table selection
2 votes · 0 comments
Reorder Schema Visualizer
2 votes · 0 comments
No comments yet.