Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-5631

Implement Reverse Key Index

        Details

        • Type: Task
        • Status: Closed
        • Priority: Major
        • Resolution: Won't Fix
        • Fix Version/s: None
        • Component/s: None
        • Labels:
          None

          Description

          First time poster... please bare with me...

          I'm looking for a reverse key index. I'm storing URLs. I could create two columns, on store the fields in reverse, but I feel a more elegant solution would be to offer a Reverse Key Index strategy.

            Gliffy Diagrams

              Attachments

                Issue Links

                is part of

                Task - A task that needs to be done. MDEV-6017 Add support for Indexes on Expressions

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Open

                  Activity

                  Ascending order - Click to sort in descending order
                  Hide
                  Permalink
                  serg Sergei Golubchik added a comment -

                  What do you mean by "reverse key index", could you elaborate on that please?

                  Show
                  serg Sergei Golubchik added a comment - What do you mean by "reverse key index", could you elaborate on that please?
                  Hide
                  Permalink
                  belugabehr BELUGABEHR added a comment -

                  I suppose this ticket should be titled to more accurately: better support for postfix indexes.

                  The issue is well covered here:

                  http://stackoverflow.com/questions/8456272/mysql-efficient-way-for-postfix-search-like-text-aka-prefix-wildcard

                  CREATE [UNIQUE|FULLTEXT|SPATIAL|REVERSE] INDEX index_name ON tbl_name (index_col_name,...)
                  Show
                  belugabehr BELUGABEHR added a comment - I suppose this ticket should be titled to more accurately: better support for postfix indexes. The issue is well covered here: http://stackoverflow.com/questions/8456272/mysql-efficient-way-for-postfix-search-like-text-aka-prefix-wildcard CREATE [UNIQUE|FULLTEXT|SPATIAL|REVERSE] INDEX index_name ON tbl_name (index_col_name,...)
                  Hide
                  Permalink
                  ampf Antonio Fernandes added a comment -

                  A workaround could be using a persistent virtual column with the reversed data and then index it... If your database is not very big (or hammered) the penalty of this solution would not be very dramatic... but each case is different

                  Show
                  ampf Antonio Fernandes added a comment - A workaround could be using a persistent virtual column with the reversed data and then index it... If your database is not very big (or hammered) the penalty of this solution would not be very dramatic... but each case is different
                  Hide
                  Permalink
                  serg Sergei Golubchik added a comment -

                  A solution to this problem would be to allow functional indexes, it's like

                  CREATE INDEX ... (REVERSE(a))

                  that is, to allow index expressions instead of columns. This is being discussed. But there're no immediate plans to have it implemented in the near future.

                  As a workaround you can, indeed, create a virtual column using this expression and create an index over it.

                  Show
                  serg Sergei Golubchik added a comment - A solution to this problem would be to allow functional indexes, it's like CREATE INDEX ... (REVERSE(a)) that is, to allow index expressions instead of columns. This is being discussed. But there're no immediate plans to have it implemented in the near future. As a workaround you can, indeed, create a virtual column using this expression and create an index over it.
                  Hide
                  Permalink
                  serg Sergei Golubchik added a comment -

                  We won't implement "REVERSE" indexes. We might implement functional indexes though.

                  Show
                  serg Sergei Golubchik added a comment - We won't implement "REVERSE" indexes. We might implement functional indexes though.

                    People

                    • Assignee:
                      Unassigned
                      Reporter:
                      belugabehr BELUGABEHR
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      3 Start watching this issue

                      Dates

                      • Due:
                        Created:
                        Updated:
                        Resolved: