"Pavel Cisar" <pcisar@...> wrote:

>
> So what you propose is a flag that would force all that would force all
> that would force all to be stored as level 1. Should be quite simple to
> implement.

Exactly.

> The problem is how at what level this flag would be defined ? At table,
> database or server level ?

At the table level.

> For table-level flag, it means new field in rdb$relations to store it.

Or better a new flag value in RDB$RELATIONS.RDB$FLAGS.

> but how this value would be set by developer ?

This is hard question. I don't have any ideas except extending DDL. And I
believe Dmitry proposed a header page flag just because he doesn't have any
good idea either ;-)

> what does is that it would introduce new config (or whatever) parameter
> to be tweaked badly, and force us one step closer to the bloat of Oracle
> and the likes.

But the "auto-tuning server" just doesn' work good in some cases and people
switch to Oracle then. This is another side of the coin. Personally, I see
no problem in having more config options or more complex DDL/DML as long as
(a) sometimes they does really useful job and (b) they're optional.


Dmitry