soundy good - I'd like such a feature as well. We'll have to limit it to a
maximum number of queries, though (50,100,200?) so the history doesn't
grow infinitely.
Andreas
> Yeah, that sounds good. It would be great if it stored the history across
> sessions too so if you close the app you can st
Yeah, that sounds good. It would be great if it stored the history across
sessions too so if you close the app you can still get to the previous
queries later.
John
My half-patch had a menu, kind of like the history menu in firefox (or
> whatever browser - I'm sure they all have it). But the sam
Dave Page wrote:
> On Wed, Sep 10, 2008 at 2:15 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
>>> I would like to have the ability the view and edit and run any query that
>>> has already been executed in the Query screen. Ideally this would keep
>>> track of queries persistently and not just for
On Wed, Sep 10, 2008 at 2:15 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
>> I would like to have the ability the view and edit and run any query that
>> has already been executed in the Query screen. Ideally this would keep
>> track of queries persistently and not just for the current session
> I would like to have the ability the view and edit and run any query that
> has already been executed in the Query screen. Ideally this would keep
> track of queries persistently and not just for the current session.
Are you describing something likevthe "history" feature in a browser?
If so
I would like to have the ability the view and edit and run any query that
has already been executed in the Query screen. Ideally this would keep
track of queries persistently and not just for the current session.
Lots of other DB management software has this; for example, Interbase 7.1+
(IBConsol
