From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Kozusznik Michal <kozusznik(dot)michal(at)ifortuna(dot)cz> |
Cc: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Query history |
Date: | 2012-07-26 07:26:12 |
Message-ID: | 1343287572.1959.20.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Thu, 2012-07-26 at 09:14 +0200, Guillaume Lelarge wrote:
> On Wed, 2012-07-25 at 22:57 +0000, Kozusznik Michal wrote:
> > > By query history, you mean the 4th tab in the query tool? or the
> > > combobox?
> >
> > I meant the combobox.
> >
>
> If you meant the combobox, it's a complete different story.
>
> The combobox doesn't get the whole query. It gets truncated at 1024
> characters per defaut.
>
> > > Well, this would be a lot of work, something not reasonable to do. The
> > > probably hardest part of it would be to find individual queries; Good
> > > luck with that.
> > >
> > > Right now, we send to the server everything or only the selected part.
> > > And we know if everything went fine, or if there was an error.
> >
> > great, so you know what to store into history. just commands sent to a server. nothing more. currently you store whole script even if single line of it has been sent.
>
> Crap, seems you're right. Working on it.
>
Fixed.
> > worse is, you store the same whole script multiple times flooding history (combo box). Inend up with all history entries filled by the same script.
> >
>
> Should not happen, this has been fixed. I'll check once the first issue
> has been fixed.
>
You're right on this too. I'll work on this when I get some time today.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Colin Beckingham | 2012-07-27 08:14:23 | SQL pane freezes while editing |
Previous Message | Guillaume Lelarge | 2012-07-26 07:14:55 | Re: Query history |