| From: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
|---|---|
| To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | [pgAdmin4][RM4017] Query Tool History persistence |
| Date: | 2019-03-12 07:00:22 |
| Message-ID: | CAM9w-_moJnzp09U1B99tWYmLAMvWdrC0NzRNfYy2ZwWtEqrmbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi Hackers,
Attached is the patch to make query history persistent. The number of
records to persist is configurable using MAX_QUERY_HIST_STORED (config.py)
which is per user/server/database based (currently set to 20). Records will
be stored in the sqlite3 db.
Test cases are included.
Kindly review.
--
Thanks and Regards,
Aditya Toshniwal
Software Engineer | EnterpriseDB Software Solutions | Pune
"Don't Complain about Heat, Plant a tree"
| Attachment | Content-Type | Size |
|---|---|---|
| RM4017.patch | application/octet-stream | 30.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raymond Mouthaan Photography | 2019-03-12 10:04:00 | pgadmin4 docker multi-arch |
| Previous Message | Khushboo Vashi | 2019-03-12 05:18:02 | [pgAdmin4][Patch] - RM 3995 - SQL view of table with trigger cause ERROR: bogus varno: 2 |