Frontend support for tables without single-column primary keys

[kgodey]

Problem

Currently, we assume that tables have single-column primary keys. We need to explicitly handle tables without primary keys or with multi-column primary keys to prevent unexpected behavior or errors.

Proposed solution

We need to make the following changes in the frontend:

• Disable infinite scroll for tables without primary keys or with multi-column primary keys. Pagination should be used instead.
• Disable editing and deleting rows for tables without primary keys or with multi-column primary keys.
• Show an informational message that tells users that some features are disabled because they have no primary key or a multi-column primary key.
  • If there is no primary key, we should show the user buttons that allow them to add a primary key field with one click or convert an existing field into a primary key field.

Additional context

• Displaying informational message based on primary key type is blocked by Backend support for tables without single-column primary keys #395

[kgodey]

@ghislaineguerin @pavish This seems like a small enough feature that we don't need a formal design for it; I suggest that when we get to it, @pavish can just implement it according to our general design patterns and @ghislaineguerin can review on the staging server and provide feedback.

[github-actions]

This issue has not been updated in 90 days and is being marked as stale.