Hi Dave,
The core patch for this project is being finalized and I am unable to work for the current few days due to issues mentioned in the previous email. Therefore, I have been thinking of what can be done in the project after this patch is done.
Below are the features I have been thinking of with a short description (ordered by priority in my point of view):
1- Supporting tables that have OIDs rather than primary keys (I have a bit of research to do about OIDs and how they work).
2- Modifying the way table information is sent from the backend, and the way they are processed in the frontend.
This will include (but is not limited to) modifying the columns info sent to the frontend to include:
- Whether the column is a primary key (instead of matching by name at the frontend).
- Whether the individual column is editable. This means there could be editable resultsets with read-only columns. It will allow for supporting a wider range of resultsets, such as: queries selecting some columns from a table in addition to an aggregation performed on one or more of the columns, queries with renamed columns, etc.
It will also include modifying how columns info is handled in the frontend.
3- Mogirfying queries generated by pgAdmin during saving data changes to be able to display them in a meaningful way to the user. Moreover, a checkbox/preferences option is to be added to enable/disable showing them in the query history (to be discussed further upon implementation). This will involve modifying the cursor and connection wrapper classes in the backend to add a mogrify function wrapper in addition to other changes throughout the code.
Please let me know what you think of this. Looking forward to feedback, suggestions and comments.
Thanks and regards.