Issue Details (XML | Word | Printable)

Key: CORE-5981
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Volker Rehn
Votes: 0
Watchers: 3

If you were logged in you would be able to see more operations.
Firebird Core

create index idx [as active | inactive] on ...

Created: 10/Jan/19 04:37 AM   Updated: 10/Jan/19 04:37 AM
Component/s: Engine
Affects Version/s: None
Fix Version/s: None

QA Status: No test

 Description  « Hide
Syncing metadata of two databases: If the master db has inactive indices which are missing in the target, on creation they will be activated in the target db, do a full data scan, and only afterwards they can then be deactivated by alter index. An optional "as active/inactive" clause would give more control over when an index is actually built. Oracle and MySQL have visible/invisible for indices, but that only removes the index from being used by the optimizer, it still performs a data scan on creation. Apparently the SQL standard does not regulate index creation. The syntax could be

INDEX indexname [AS ACTIVE | INACTIVE] ON tablename
{(col [, col ...]) | COMPUTED BY (<expression>)};

ACTIVE being the default as it is now. Similar to how triggers are defined.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.