Den 2013-08-13 06:52 skrev Dmitry Yemanov såhär:
All,
There are some kinds of queries that have data access methods linked to
each other. Windowed functions are the obvious example, but it happens
even for regular aggregate functions. For example, COUNT(DISTINCT) needs
not only read the
Dmitry Yemanov firebi...@yandex.ru писал(а) в своём письме Tue, 13 Aug
2013 08:52:02 +0400:
Select Expression
1: - Aggregate
2:- Table RDB$RELATIONS Access By ID
3: - Index RDB$INDEX_0 Scan
4:- Sort (unique)
5: - $(2)
all methods are globally enumerated. The output
13.08.2013 6:52, Dmitry Yemanov wrote:
Comments anyone? Other suggestions?
Because plans are read from bottom to the top, I would prefer something like
this:
(A)
Select Expression
- Aggregate
- Sort (unique)
- Table RDB$RELATIONS Access By ID
- Index RDB$INDEX_0
13.08.2013 11:55, Dimitry Sibiryakov wrote:
Because plans are read from bottom to the top, I would prefer something like
this:
(A)
Select Expression
- Aggregate
- Sort (unique)
- Table RDB$RELATIONS Access By ID
- Index RDB$INDEX_0 Scan
Now imagine two
13.08.2013 10:07, Dmitry Yemanov wrote:
Select Expression
- Aggregate
- Sort (unique)
- Sort (unique)
- Table RDB$RELATIONS Access By ID
- Index RDB$INDEX_0 Scan
Is it understandable that sorts are independent from each other but both
dependent
Unable to read MON$-tables when run few ISQLs that all make bulk updates of
huge table (10E8 rows for each of them)
---
Key: CORE-4179
URL:
Den 2013-08-13 10:23 skrev Dimitry Sibiryakov såhär:
13.08.2013 10:07, Dmitry Yemanov wrote:
Select Expression
- Aggregate
- Sort (unique)
- Sort (unique)
- Table RDB$RELATIONS Access By ID
- Index RDB$INDEX_0 Scan
Is it understandable that
Wrong results after creating collation or win1251 from unicode case
insensitive: strings are considered as distinct while they don't
Key:
