Discussion about Views and Models (pre-implementation)

@shreya1771 - This is what I roughly I've in mind regarding the minor details of tabulator. Let's discuss about any improvements below, before starting with the Rails App. 😄

### Front-end / Views

- The "route" for each table will be `{user_email_id}/{table_id}`.

- [This example](https://editor.datatables.net/examples/styling/semanticui.html) is roughly what I've in mind for each table. The add, edit and delete options are provided for each row. There should also be same features for each column as well. Also, there'll be searching, pagination and "Show x entries per page" dropdown too.

- The list of all tables will also be presented as a similar view, with columns being table name, number of rows, number of columns and brief description.

- It'd also help to have "Import from" / "Export into" buttons [as shown here](https://datatables.net/extensions/buttons/examples/styling/semanticui.html) (These parts will be done by daru-io). We'll use daru's dataframes as intermediate data structure in the Controllers.

### Back-end / Models

- Model user : Should contain user_id, user_name, user_email_id and user_password.

- Model table : Should contain table_id, table_name, user_email_id, sharing (private or public or particular email ids)

- Model table_access : Should contain table_id, table_accessors (Array of user_ids, that have access to table_id table)

- Model columns : Should contain col_id, table_id, table_column_name, table_column_type

- Model rows : Should contain row_id, table_id, row_data (Array)

No files, tests, or entry points are named. Start by turning the proposed views, route, models, and access rules into an agreed implementation plan; the work is not ready to assess as done until the discussion settles scope and acceptance criteria.

Written by the indexing model from the issue text.