08.01.2014 10:30, liviusliv...@poczta.onet.pl wrote:
> Why plan can not by extended for hint purposes?
It can, the question is whether it should.
> This is natural placefor FB users to tell optimizer
> the better way of query execution.
Personally, I see an important difference between planning
08.01.2014 00:49, Mark Rotteveel wrote:
>
> I do think you should consider the implications of having full featured
> hints in the future, if only not to make a poor choice now when it comes
> to syntax.
And I suggested how the OPTIMIZE clause can be extended later, if required.
Dmitry
---
>>I'd suggest to let the legacy PLAN resting in piece. It's already misses many
>>optimizer features and will outdate more and more with years.
Hi, Dmitry
Why plan can not by extended for hint purposes? This is natural place for FB
users to tell optimizer the better way of query execution. Thi
On 7-1-2014 16:07, Dmitry Yemanov wrote:
> Kjell,
>
>> This makes sense, but I also think what Jim Starkey said makes sense,
>> i.e. that introducing optimizer hints in essence means you've given up
>> on creating a good automatic optimizer.
>
> Jim is not alone in thinking this way. This is why I
On 7-1-2014 20:21, Jim Starkey wrote:
> On 1/7/2014 1:14 PM, Simonov Denis wrote:
>>> Why it have to have fixed position? Cannot btyacc syntax parser handle a
>>> clause anywhere?..
>>
>> Course parser can parse and tips from various places, but I look at it
>>from the perspective of the applic
On 1/7/2014 1:14 PM, Simonov Denis wrote:
>> Why it have to have fixed position? Cannot btyacc syntax parser handle a
>> clause anywhere?..
>
> Course parser can parse and tips from various places, but I look at it
> from the perspective of the application developer. It is much easier to
> remove
>>> I would not give up the compiled binary (for Windows x86). Very
>>> interesting to compare the performance of cold filling cache.
>>
>>I'll prepare binaries at this weekend.
>
>Here they are:
>
> http://web.firebirdsql.org/downloads/rabbits/hvlad/Firebird-3.0.0.30811_Win32-Extents.
> Why it have to have fixed position? Cannot btyacc syntax parser handle a
> clause anywhere?..
Course parser can parse and tips from various places, but I look at it
from the perspective of the application developer. It is much easier to
remove or comment out the tips when they are conce
07.01.2014 17:12, Simonov Denis wrote:
> as a place to OPTIMIZE ... I suggest at the end
> of SQL query as well as for the plan.
Why it have to have fixed position? Cannot btyacc syntax parser handle a
clause anywhere?..
--
WBR, SD.
-
Kjell Rilbe писал(а) в своём письме Tue, 07 Jan
2014 18:40:08 +0400:
I agree with Dimitri. Direction plan entirely and hints for the optimizer
should be separated. But as a place to OPTIMIZE ... I suggest at the end
of SQL query as well as for the plan.
--
Написано в почтовом клиенте бра
Kjell,
> This makes sense, but I also think what Jim Starkey said makes sense,
> i.e. that introducing optimizer hints in essence means you've given up
> on creating a good automatic optimizer.
Jim is not alone in thinking this way. This is why I explicitly
mentioned that I don't want to discuss
I've been following this thread with interest. I can't resist entering
my humble opinion.
Den 2014-01-07 10:38 skrev Mark Rotteveel såhär:
> As I see it, optimizer hints are a different beast from limiting the
> result set using FIRST. The first is a way to influence decisions of the
> optimizer,
On Tue, 07 Jan 2014 12:28:11 +0400, Alex wrote:
>> So, historically, no, it's neither a workaround nor a hack. Parsing
SQL
>> comments ... that sounds like a hack to me. Adding yet another
>> non-standard keyword when one already exists and does what you want
>> doesn't appeal all that much eit
07.01.2014 13:25, Simonov Denis пишет:
>
> Strategy ALL ROWS default optimizer I consider correct. Nevertheless, I
> believe that it is necessary to introduce a parameter in the configuration
> database level which could be returned to the old behavior where the
> optimizer to use a strategy FIRST
On Mon, 6 Jan 2014 11:38:32 -0500, Ann Harrison wrote:
> The FIRST keyword was added to Firebird's SQL in version 1.0 or 1.1 -
> in 2000 0r 2001, but the use of FIRST in InterBase goes back much
further.
> It was part of GDML - and it's purpose was to signal that the query
should
> be optimized to
07.01.2014 12:46, Dmitry Yemanov wrote:
>
> It *is* related as soon as you need to alter from the default FIRST ROWS
> to custom FIRST ROWS in some particular query.
Read: "custom ALL ROWS", sorry.
Dmitry
--
Rapidly t
>
> 5) ALL ROWS mode is the default one for queries without FIRST / ROWS
> clause. Whether the default mode can be altered per database (via
> configuration file) or per session is discussable.
>
> Dmitry
Strategy ALL ROWS default optimizer I consider correct. Nevertheless, I
believe that it is
Notes on database security assesment
http://www.slideshare.net/qqlan/firebird-interbase-database-engine-hacks-or-rtfm
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a c
07.01.2014 12:28, Alex wrote:
> Or even config file option. Not related with SQL IMHO.
It *is* related as soon as you need to alter from the default FIRST ROWS
to custom FIRST ROWS in some particular query.
Dmitry
--
Ann,
> The FIRST keyword was added to Firebird's SQL in version 1.0 or 1.1 -
> in 2000 0r 2001, but the use of FIRST in InterBase goes back much further.
> It was part of GDML - and it's purpose was to signal that the query should
> be optimized to walk the index (navigate, in the internals) rathe
On 01/06/2014 08:38 PM, Ann Harrison wrote:
Dmitry,
> Right. And if you want to give the optimizer a hint that it
should choose
> the second plan, change the query like this:
>
> select first 100 * from MOVIES where COMMENTS like '%yacht%
order
> by NAME;
>
Ann Harrison писал(а) в своём письме Mon, 06 Jan 2014
20:38:32 +0400:
> The FIRST keyword was added to Firebird's SQL in version 1.0 or 1.1 -
> in 2000 0r 2001, but the use of FIRST in InterBase goes back much
> further.
> It was part of GDML - and it's purpose was to signal that the query
22 matches
Mail list logo
