From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Maciej Gajewski <maciej(dot)gajewski0(at)gmail(dot)com> |
Cc: | ian link <ian(at)ilink(dot)io>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Review: query result history in psql |
Date: | 2013-06-28 15:49:28 |
Message-ID: | CAFj8pRAiWL79DStWt=qOiSmXrpgVEynpMQ=Jz0qiQ6nQxjgL5w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello
I am not sure, this interface is really user friendly
there is not possible "searching" in history, and not every query push
to history some interesting content.
It require:
* simply decision if content should be stored in history or not,
* simply remove last entry (table) of history
* queries should be joined to content, only name is not enough
Regards
Pavel
2013/6/28 Maciej Gajewski <maciej(dot)gajewski0(at)gmail(dot)com>:
> Thanks for checking the patch!
>
> So what's left to fix?
> * Moving the escaping-related functions to separate module,
> * applying your corrections.
>
> Did I missed anything?
>
> I'll submit corrected patch after the weekend.
>
> M
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-06-28 15:52:15 | Re: changeset generation v5-01 - Patches & git tree |
Previous Message | Alvaro Herrera | 2013-06-28 15:41:57 | Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls |