Re: [Firebird-devel] Explained plan output: feedback wanted

2013-08-13 Thread Kjell Rilbe
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

Re: [Firebird-devel] Explained plan output: feedback wanted

2013-08-13 Thread Simonov Denis
Dmitry Yemanov писал(а) в своём письме 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 is

Re: [Firebird-devel] Explained plan output: feedback wanted

2013-08-13 Thread Dimitry Sibiryakov
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$INDE

Re: [Firebird-devel] Explained plan output: feedback wanted

2013-08-13 Thread Dmitry Yemanov
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 No

Re: [Firebird-devel] Explained plan output: feedback wanted

2013-08-13 Thread Dmitry Yemanov
13.08.2013 11:28, Kjell Rilbe wrote: > > I fear that I know too little about the inner workings, but I'm a bit > surprised... I would have thought that this is what actually happens: > > Select Expression > -> Aggregate >-> Sort (unique) > -> Table "RDB$RELATIONS" Access By ID

Re: [Firebird-devel] Explained plan output: feedback wanted

2013-08-13 Thread Dimitry Sibiryakov
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

[Firebird-devel] [FB-Tracker] Created: (CORE-4179) Unable to read MON$-tables when run few ISQLs that all make bulk updates of huge table (10E8 rows for each of them)

2013-08-13 Thread Pavel Zotov (JIRA)
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: http://trac

Re: [Firebird-devel] Explained plan output: feedback wanted

2013-08-13 Thread Kjell Rilbe
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

[Firebird-devel] [FB-Tracker] Created: (CORE-4180) Wrong results after creating collation or win1251 from unicode case insensitive: strings are considered as distinct while they don't

2013-08-13 Thread Pavel Zotov (JIRA)
Wrong results after creating collation or win1251 from unicode case insensitive: strings are considered as distinct while they don't Key: CORE-4180

[Firebird-devel] [FB-Tracker] Created: (CORE-4181) isql should be able to use the new API

2013-08-13 Thread Simonov Denis (JIRA)
isql should be able to use the new API -- Key: CORE-4181 URL: http://tracker.firebirdsql.org/browse/CORE-4181 Project: Firebird Core Issue Type: Improvement Components: ISQL Affects Versions: