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 was in the process of creating an implementation plan to fix the bug where column comments in the Postgres table structure view are showing as (NULL) instead of the actual comments. I have identified that the issue might be in the 'listTableColumns' function in the '/apps/studio/src/lib/db/clients/postgresql.ts' file, which fetches the table structure from the database but doesn't fetch the column comments. I have created a step to modify this function to fetch the column comments. However, I didn't have enough time to create a step to modify the 'tableData' computed property in the 'TableSchema.vue' file to include the column comments in the data passed to the Tabulator component. I would appreciate if someone could help with this. Thank you.
Implementation proposal (work in progress)
Step 1: Modify the 'listTableColumns' function to fetch column comments
In the '/apps/studio/src/lib/db/clients/postgresql.ts' file, modify the 'listTableColumns' function to fetch the column comments from the Postgres database. Add 'column_comment' to the SELECT clause of the SQL query. Map the 'column_comment' field to the 'comment' property of the returned objects. Make sure to handle any errors and edge cases, and to adhere to the existing code style and conventions.
For more information about Ellipsis, check the documentation.
Describe the bug
When choosing "View Structure" on a postgres table, none of the column comments appear, simply showing
(NULL)
instead.To Reproduce
Steps to reproduce the behavior:
View Structure
Expected behavior
Comments should appear
Screenshots / Gifs
If applicable, add screenshots or GIFS to help explain your problem.
Version Information (please complete the following information):
Additional context
Pretty sure this was working in a previous version
The text was updated successfully, but these errors were encountered: