W dniu 2015-03-09 19:27:59 użytkownik Dmitry Yemanov <firebi...@yandex.ru> napisał: > 09.03.2015 17:06, liviuslivius wrote: > > > > what is the difference between > > Index "ROZLICZENIE_FK1" Range Scan (lower bound: 1/1, upper bound: 1/1) > > When you see "lower/upper bound: N/M", this is a "less/greater/between" > scan. Each boundary condition may use N of M segments. > > > Index "RODZAJ_DZIAL_FK" Range Scan (partial match: 1/2) > > When you see "partial match: N/M", this means an equality scan (using N > of M segments). Yet another case is "full match" which also means an > equality scan but the one uses all index segments. > > > Dmitry > >
Hi, is possible to extend this to show Range Scan (lower bound: 1/1, upper bound: 1/1) + (partial match: 1/2) like Range Scan (partial match: 1/2, lower bound: 1/1, upper bound: 1/1) e.g. compound index CREATE INDEX INDEX_NAME AAA ON XXX(A, B); SELECT * FROM XXX X WHERE X.A>10 AND X.A<15 here we have partial index use(only A field) but also lower/upper bound regards, Karol Bieniaszewski ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
