snapshot_comments

2 rows where snapshot_pk = 18

✎ 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
34 18 18 1 106255287914 - 2025-06-07T09:25:00Z - Call Centre Satisfied {"id": "106255287914", "mobile_number": "-", "posted_by": "Call Centre", "remarks": "Satisfied", "status": "-", "time_stamp": "07-JUN-2025 14:55:00"}
35 18 18 2 106255287914 9182954615 2025-06-04T10:58:21Z Attended By Officer P.Venkateshwar Goud rectified sir {"id": "106255287914", "mobile_number": "9182954615", "posted_by": "P.Venkateshwar Goud", "remarks": "rectified sir", "status": "Attended By Officer", "time_stamp": "04-JUN-2025 16:28:21"}

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)
);