snapshot_comments

2 rows where snapshot_pk = 16

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: comment_timestamp (date)

comment_pk ▼ snapshot_pk ordinal complaint_id mobile_number comment_timestamp status_text posted_by remarks raw_comment_json
27 16 16 1 103255140312 - 2025-04-20T10:37:18Z - Call Centre Satisfied {"id": "103255140312", "mobile_number": "-", "posted_by": "Call Centre", "remarks": "Satisfied", "status": "-", "time_stamp": "20-APR-2025 16:07:18"}
28 16 16 2 103255140312 9121242764 2025-04-11T12:07:19Z Attended By Officer P Anusha rectified {"id": "103255140312", "mobile_number": "9121242764", "posted_by": "P Anusha", "remarks": "rectified", "status": "Attended By Officer", "time_stamp": "11-APR-2025 17:37:19"}

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE snapshot_comments (
    comment_pk INTEGER PRIMARY KEY,
    snapshot_pk INTEGER NOT NULL REFERENCES complaint_snapshots(snapshot_pk) ON DELETE CASCADE,
    ordinal INTEGER NOT NULL,
    complaint_id TEXT NOT NULL,
    mobile_number TEXT NOT NULL,
    comment_timestamp TEXT NOT NULL,
    status_text TEXT NOT NULL,
    posted_by TEXT NOT NULL,
    remarks TEXT NOT NULL,
    raw_comment_json TEXT NOT NULL,
    UNIQUE(snapshot_pk, ordinal)
);