25.04.2016 10:35, Christian Waldmann wrote:
> In Firebird CORE-659 (http://tracker.firebirdsql.org/browse/CORE-659) there
> is a collection of requests for spatial index, e.g. R*Tree or GiST, for GIS
> applications and other. Spatial indexes are also fine to find events in a
> interval of time.
>
On Mon, Apr 11, 2016 at 7:40 AM, Dimitry Sibiryakov
wrote:
> 11.04.2016 13:28, Dmitry Yemanov wrote:
> > But it can be made possible. The question is whether it's worth it.
>
>While bug with orphan index nodes is living in the engine - index only
> scan is
> impossible
>
>
>
> >
> > This optimization can only be done if constant conditions are in the
> > SQL, so +0 like tricks would not be affected.
>
> I already considered that, it seems easy enough to implement.
>
>
>
>
Worth having?
--
Regards,
Atri
*l'apprenant*
On Mon, Apr 11, 2016 at 6:15 PM, Dmitry Yemanov wrote:
> 11.04.2016 14:40, Dimitry Sibiryakov wrote:
> >
> > While bug with orphan index nodes is living in the engine - index only
> scan is
> > impossible completely.
>
> Pure index-only scan - maybe. It's impossible without
11.04.2016 14:40, Dimitry Sibiryakov wrote:
>
> While bug with orphan index nodes is living in the engine - index only scan is
> impossible completely.
Pure index-only scan - maybe. It's impossible without transaction
numbers in indices too. But there may be other alternatives to consider.
>
11.04.2016 13:28, Dmitry Yemanov wrote:
> But it can be made possible. The question is whether it's worth it.
While bug with orphan index nodes is living in the engine - index only scan
is
impossible completely.
Transformation numeric->double can loose data. Using integers as a key will
11.04.2016 14:16, Dimitry Sibiryakov wrote:
> 11.04.2016 13:08, Molnár Attila wrote:
>> It's hard and costly (or even possible) to deconstruct the index format to
>> get the
>> original column values?
>
> Yes, in common case it is impossible.
But it can be made possible. The question is whether
11.04.2016 14:08, Molnár Attila wrote:
>
>> When InterBase was created, there was a lot of academic work on
>> optimizing corner cases, with the result that academic databases
>> tended to spend more time optimizing than retrieving. We made the
>> deliberate choice not to spend optimizer time
11.04.2016 13:08, Molnár Attila wrote:
> It's hard and costly (or even possible) to deconstruct the index format to
> get the
> original column values?
Yes, in common case it is impossible.
--
WBR, SD.
--
Find
On 2016.04.09. 20:25, Ann Harrison
wrote:
On Fri, Apr 8, 2016 at 5:54 AM,
Molnár Attila
wrote:
Optimizations
On Fri, Apr 8, 2016 at 5:54 AM, Molnár Attila wrote:
>
>
> *O*
> *ptimizations*- IS NOT NULL should use index. It is equivalent with
> >= min_value or <= max_value based on index direction
>
Histograms and clustered indexes (if they're being considered) could help
here to
Hi Dmitry!
Hope never dies. I prefer optimizations over the other new features. ;)
Thanks for the reply.
On 2016.04.08. 12:30, Dmitry Yemanov wrote:
> 08.04.2016 12:54, Molnár Attila wrote:
>> Here is my list.
> List of v4 features is already composed. We may add some more
> improvements here
08.04.2016 12:54, Molnár Attila wrote:
>
> Here is my list.
List of v4 features is already composed. We may add some more
improvements here and there, but no promises about them.
Dmitry
--
Firebird-Devel mailing
13 matches
Mail list logo