Hi,
> On Tue, Oct 17, 2017 at 1:44 PM, Tomek wrote:
>
>> Hi,
>>
>>>>>> It is not exactly truth... In v3 the query is executed, fetched and all
>>>>>> rows are displayed,
>>>>>
>>>>> No they're not, thoug
and about 500 Mb of memory (v3 used
around 80)... What is more in v4 I can't get 30 records even with default
ON_DEMAND_RECORD_COUNT (canceled query after 5 minutes) while v3 managed to do
it in 80 seconds.
I understand that large results are rare but this is a management tool not some
office app... It should do what I want...
And again You are telling me what I want and what I need, and how I should do
it... You decided to make this tool in a way that no other db management works,
You cut out a lot of v3 features, You purposely limit usability to account for
poor performance and call it a feature...
It reminds me of some big software company in old days...
--
Tomek
e are the users) who are happy that selecting 1
rows requires dragging scrollbar five times to see 5001 record...
Saying pointless I meant that if I want 1 rows I should get 1 rows, if
I want to limit my data I'll use LIMIT. But if the ui can't handle big results
just give me easiest/fastest way to get to may data.
--
Tomek
ebapp...
And by the way You have a big leak in query tool - execute query with several
thousands rows, scroll above 1000 mark few times, execute the same query,
scroll above 1000 mark few times - repeat until You run out of memory or v4
crashes...
--
Tomek
