Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bitmap Index [CORE2057] #2493

Open
firebird-automations opened this issue Aug 28, 2008 · 5 comments
Open

Bitmap Index [CORE2057] #2493

firebird-automations opened this issue Aug 28, 2008 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Stefan Kinnen (ncc1701)

In some Cases it can be usefull to create a bitmap index on a table field e. g. rows with only some difficult values (e. g. 4 or 5) and you have to search on it. I'm knowing that Oracle has this feature.

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

Please explain further.

Firebird currently creates all indexes as bitmaps, so I don't understand what change you are looking for.

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

Never used it, but accordingly to Oracle documentation, its bitmap index seems crap. It's read-only and probably just for OLAP usage.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Well, Firebird does not create indices as bitmaps. Neither they're read-only in Oracle.

But I agree this feature is of somewhat limited use. It makes sense only for columns with extremely low selectivities which data is modified rarely (because of high maintaining cost for a bitmap index).

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

priority: Major [ 3 ] => Minor [ 4 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Thiago Borges (thborges)

And what about bitmap join index?
I have recently solved performance issues in Oracle with this type of index.
The relations in my case are PARTS and ITEMS. I need to query them filtering a interval on PARTS.DATE and a specific ITEMS.PRODUCT. Each field is in one of the tables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant