Hello.
The background of this task in CORE-5612, it contains research details and
conclusions.
How much I understood, there is no way to specify what index should be used
at system inquiries from *.epp files?
If not, is it possible to enable the create/delete, enable/disable indexes
on system tables, including standard system indexes?
In Firebird 2.5, we get around the problem described in CORE-5612 by
creating 2 indexes and turning off the indices RDB$INDEX_27 and
RDB$INDEX_28 at the right time (then turn it back on).
But we can not act in the same way in Firebird 3.0 because these actions
are only allowed by GBACK (attachment->isGbak) and only during the creation
of the database (attachment->att_flags & ATT_creator).
Those if you do not want to allow such actions publicly, you could be
allowed to do it from external utilities similar to GBACK
(dpb.insertString(isc_dpb_gbak_attach, FB_VERSION, fb_strlen(FB_VERSION))),
but then you need to remove the check for the creator of database
(attachment->att_flags & ATT_creator).
2018-02-19 16:38 GMT+03:00 Rashid Abzalov (JIRA) <trac...@firebirdsql.org>:
>
> [ http://tracker.firebirdsql.org/browse/CORE-5746?page=com.
> atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Rashid Abzalov updated CORE-5746:
> ---------------------------------
>
> Description:
> Proceeding from the fact that it is necessary to apply adaptive mechanics,
> and from the fact that in the source code is not used anywhere specifying
> the plan (perhaps there are reasons for it) - there is hardly a chance that
> you implement the use of "correct" system indexes in the right places.
> Therefore, please remove the restriction on creating indexes for system
> tables, and disabling/enabling system indexes.
> We ourselves will manipulate them at the right time.
>
> In the end, what can be a bad from modification of system indexes, given
> that DB developers understand what they are doing?
> For example, in Oracle there are no restrictions in modifying the system
> tables - even insert into dual table, not to mention the creation of
> indexes.
>
> Of course, we are can find a way around this restriction
> (check_gbak_cheating_insupd, check_gbak_cheating_delete), but why can not
> you provide a regular way?
>
> was:
> Proceeding from the fact that it is necessary to apply adaptive mechanics,
> and from the fact that in the source code is not used anywhere specifying
> the plan (perhaps there are reasons for it) - there is hardly a chance that
> you implement the use of "correct" system indexes in the right places.
> Therefore, please remove the restriction on creating indexes for system
> tables, and disabling/enabling system indexes.
> We ourselves will manipulate them at the right time.
>
> In the end, what can be a bad from modification of system indexes, given
> that DB developers understand what they are doing?
> For example, in Oracle there are no restrictions in modifying the system
> tables - even insert into dual table, not to mention the creation of
> indexes.
>
> Of course, you can find a way around this restriction
> (check_gbak_cheating_insupd, check_gbak_cheating_delete), but why can not
> you provide a regular way?
>
>
> > Remove the restriction on create/delete, enable/disable the system
> indexes in system tables
> > ------------------------------------------------------------
> -------------------------------
> >
> > Key: CORE-5746
> > URL: http://tracker.firebirdsql.org/browse/CORE-5746
> > Project: Firebird Core
> > Issue Type: Sub-task
> > Components: Engine
> > Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.0.3
> > Reporter: Rashid Abzalov
> >
> > Proceeding from the fact that it is necessary to apply adaptive
> mechanics, and from the fact that in the source code is not used anywhere
> specifying the plan (perhaps there are reasons for it) - there is hardly a
> chance that you implement the use of "correct" system indexes in the right
> places.
> > Therefore, please remove the restriction on creating indexes for system
> tables, and disabling/enabling system indexes.
> > We ourselves will manipulate them at the right time.
> > In the end, what can be a bad from modification of system indexes, given
> that DB developers understand what they are doing?
> > For example, in Oracle there are no restrictions in modifying the system
> tables - even insert into dual table, not to mention the creation of
> indexes.
> > Of course, we are can find a way around this restriction
> (check_gbak_cheating_insupd, check_gbak_cheating_delete), but why can not
> you provide a regular way?
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://tracker.firebirdsql.org/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
