> By query history, you mean the 4th tab in the query tool? or the
> combobox?
I meant the combobox.
> 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 s
On Tue, 2012-07-24 at 18:41 -0300, Daniel Serodio (lists) wrote:
> Horizontal scroll using the mouse wheel (while holding Shift) or by
> dragging on the touchpad with two fingers doesn't work on OS X. I can
> only scroll horizontally using the scrollbar.
>
Dave, can you check this? and fix if n
On Wed, 2012-07-25 at 18:15 +0200, Michal Kozusznik wrote:
> While trying to use query history, I found 2 issue limiting the power
> of this feature:
>
By query history, you mean the 4th tab in the query tool? or the
combobox?
> A)
> query history is filled by whole script, not only but queri
On Wed, 2012-07-25 at 16:13 +0400, Vjacheslav A. wrote:
> Hi,
>
> in data view when a query returns error, message isn't displayed,
> create 2 table table1 and table2, then open table1 data view with filter:
> id=(SELECT table1_id FROM table2),
> an empty grid appears, maybe better to display erro
On Wed, 2012-07-25 at 12:15 +0400, Vjacheslav A. wrote:
> I often need edit some data, and i run data view with some filter,
> and often before edit I need some computations (run aggregate functions) or
> check records,
> and this time I run query tool and write a query,
> for me it will be more co
While trying to use query history, I found 2 issue limiting the power
of this feature:
A)
query history is filled by whole script, not only but queries run. It
fills query history by the same script multiple times even if script is
not changing.
How to reproduce:
1. Use following script
SEL
Hi,
in data view when a query returns error, message isn't displayed,
create 2 table table1 and table2, then open table1 data view with filter:
id=(SELECT table1_id FROM table2),
an empty grid appears, maybe better to display error message (query has an
error: "more than one row returned by a subq
I often need edit some data, and i run data view with some filter,
and often before edit I need some computations (run aggregate functions) or
check records,
and this time I run query tool and write a query,
for me it will be more comfortable to click one button in same window to
launch query tool.
