Easily store user-defined order of your ActiveRecord models utilizing lexicographical sorting. A live demo is available here.
Inspired by Atlassian's Lexorank.
Add this line to your application's Gemfile:
gem 'lexorank'
gem 'with_advisory_lock' # recommended to get locking out of the boxAnd then execute:
$ bundle install
Your model will need a database column storing the rank. The default ranking column is called rank, however you are free to change that (see rank!).
One way to add this in a rails application is to generate a simple migration:
$ rails g migration AddRankTo<insert model name here> rank:text:uniq
This should generate a migration like that:
class AddRankToPages < ActiveRecord::Migration[7.0]
def change
add_column :pages, :rank, :text
add_index :pages, :rank, unique: true
end
endImportant: After the migration was created, take a look at the following paragraphs highlighting differences between the different database adapters:
After applying the specific options just run the migration using:
$ rails db:migrate
It's important to choose a binary collation for the database column.
The simplest one to use, which we recommend and test against, is the ascii_bin collation.
You can specify it like this:
class AddRankToPages < ActiveRecord::Migration[7.0]
def change
add_column :pages, :rank, :text, collation: 'ascii_bin'
add_index :pages, :rank, unique: true
end
endIt's important to use the C collation which supports ordering in the same way ruby does for strings.
You can specify it like this:
You can specify it like this:
class AddRankToPages < ActiveRecord::Migration[7.0]
def change
add_column :pages, :rank, :text, collation: 'C'
add_index :pages, :rank, unique: true
end
endThere are no additional steps needed if you use SQLite.
In your model require lexorank/rankable. Afterwards, you will be able to use the rank! method like this:
require 'lexorank/rankable'
class Post < ActiveRecord::Base
rank!
endNow you have access to the following methods:
# Return all pages in the supplied order
Page.ranked
page = Page.first
# Moves this page instance to the second position
page.move_to(1)
# Alias to page.move_to(0)
page.move_to_topKeep in mind that a newly created record will not have a rank by default. Just manually move it to the position you want it to be.
Alternatively you can setup a before_create callback like this:
Expand
require 'lexorank/rankable'
class Page < ActiveRecord::Base
rank!
before_create do
self.move_to_top
end
endrank!(field: :rank, group_by: nil, advisory_lock: {})
This is the entry point to use lexorank in your model.
Options:
field: Allows you to pass a custom field which is being used to store the models rank. (defaults to:rank)group_by: Makes it possible to split model ordering into groups by a specific column. Learn moreadvisory_lock: The advisory lock configuration. Learn more
ranked(direction: :asc)
This is a model scope which will return the ordered collection.
This will only be available if your model calls rank! before. The scope will exclude all models that have no rank set.
Options:
direction: Allows you to pass the orders direction. SeeActiveRecord::QueryMethods::VALID_DIRECTIONSfor possible values. (defaults to:asc)
Those will only be available if your model calls rank! before.
move_to(position, **options, &block)
This method will set your object's rank column according to the new position. Position counts start at zero. This will not persist the rank to the database.
The options passed can be used to configure the ranking operation. Currently it is only possible to pass options related to Locking. When passing a configuration hash under the :advisory_lock key one can pass additional options to ::with_advisory_lock.
The passed block will be executed after the new rank was assigned.
When using Locking it is discouraged to use move_to without passing a block. The block will be executed inside of the advisory lock and should persist the change to the rank to ensure that no positioning conflicts will occur.
move_to_top(**options, &block)
Alias to move_to(0, ...)
move_to_end(**options, &block)Like move_to but moves the element to the end of the collection.
move_to!(position, **options)
Like move_to. However, this methods persists the rank to the database directly.
If an update is needed, the method will return the result of save, otherwise true.
move_to_top!(**options)
Like move_to! but moves the element to the top of the collection.
move_to_end!(**options)Like move_to! but moves the element to the end of the collection.
no_rank?
Returns true if the ranking field is nil. This means that the model has no rank yet.
Often times you come in a situation where you don't want to order all items in one collection. Lexorank will take care of this by grouping your models by a specified column. This is especially interesting when your model is associated with another one.
Consider the following example:
# page.rb
class Page < ActiveRecord::Base
has_many :paragraphs
end
# paragraph.rb
class Paragraph < ActiveRecord::Base
belongs_to :page
endWhen adding lexorank to your paragraph model, ordering would not be page dependent. Instead the whole collection will be considered when moving or retrieving the models via lexorank.
The solution is the group_by option of the rank! method, which will allow a column or an association name.
Change your paragraph model like this:
require 'lexorank/rankable'
class Paragraph < ActiveRecord::Base
belongs_to :page
rank!(group_by: :page)
endWhen moving a paragraph via the instance methods only paragraphs of the model's page will be considered.
Please keep in mind that lexorank can only find the association when you put rank! after the association definition.
Alternatively, you can supply the column directly:
require 'lexorank/rankable'
class Paragraph < ActiveRecord::Base
rank!(group_by: :page_id)
belongs_to :page
endThis means that grouping is completely independent of associations and can also be used without them.
Retrieving data in a grouped manner is as simple as utilizing built-in ActiveRecord behavior of scopes:
# This will return all paragraphs of the first page in the supplied order.
Page.first.paragraphs.rankedSince version 0.2.0 lexorank ships with advisory locking by default. Advisory locks are a locking mechanism on the database level that ensures that only one record in a collection can change their rank at a time. This is important to prevent two records being assigned the same rank.
Advisory locking is enabled by default if the model class responds to the ::with_advisory_lock method. The easiest way to achieve this is by installing the incredible with_advisory_lock gem.
It is also possible to implement advisory locking yourself. The with_adivsory_lock method must accept one name argument and arbitrary keyword arguments similar to the signature of the with_advisory_lock gem.
With advisory locking enabled it is actively dicouraged to call move_to or move_to_top without a block. This is because those methods do not persist to the database and thus cannot acquire a lock. Make sure the bang equivalents or pass a block in which the record is persisted.
If you manage locking yourself or you do not need locking, you can disable advisory locks:
class Page < ActiveRecord::Base
rank!(advisory_lock: { enabled: false })
endNote that locking will be disabled by default if the model class does not respond to the with_advisory_lock method.
The lexorank gem will choose an appropriate lock name by taking the class name, the ranking column and grouping into account. It's still possible to supply a lock_name callable that returns a custom name.
class Page < ActiveRecord::Base
rank!(advisory_lock: { lock_name: ->(page) { "custom_lock_for_page_#{page.id}" } })
endAlso it's possible to pass other options (e.g. timeout_seconds when using the with_advisory_lock gem). All options are passed to the with_advisory_lock method as keyword arguments.
class Page < ActiveRecord::Base
rank!(advisory_lock: { timeout_seconds: 3 })
endIf an option needs to be applied for a single ranking operation only, you can directly pass additional options to all move_to methods using the :advisory_lock key. Those will overwrite all options set using rank!.
class Page < ActiveRecord::Base
rank!(advisory_lock: { timeout_seconds: 3 })
end
# We might need a higher timeout here so we overwrite the initial configuration.
Page.new.move_to_top!(advisory_lock: { timeout_seconds: 30 })The gem works quite simple. When calling move_to the gem will identify the item which is on the wanted position and the one before.
Afterwards, a simple function searches for a rank which is between the ranks of the two items.
For example: We want to move a currently unranked item to position 1 which means it should be the second element when calling ranked (because positions start at 0).
The gem will look for the element on position 0 and on position 1. When we position our item between those two we'll achieve the wanted position.
Let's say the items have the ranks 'A' and 'C'. The gem will give our item the position 'B' as it is between the other two.
Let's say we want to find a rank between 'A' and 'B'. There is no character in between, which means the gem chooses the new rank value 'AU'. It chooses 'U' because it's the middle between 'z' (highest possible character) and '0' (lowest possible character).
This also means, that given a huge amount of items and frequent moves to similar positions can result to long rank values which will make ordering slower (see Performance). The solution to this problem is rebalancing all rank values, which currently isn't implemented in this gem.
Disclaimer: I'm kinda new to benchmarking. Feel free to give tips or advice on the current implementations.
All tests were run with the following setup: ActiveRecord with SQLite on WSL2 running ruby 3.0.0
Because of possible unbalanced ranks, receiving data from the database can slow down. To demonstrate this there is a benchmark which will compare receiving data from a balanced set of x items against an unbalanced set of x items.
Results with 100,000 items
Rehearsal ----------------------------------------------------
Unbalanced: 1.009327 0.190001 1.199328 ( 1.199330)
Balanced: 0.605503 0.039992 0.645495 ( 0.645499)
------------------------------------------- total: 1.845495sec
user system total real
Unbalanced: 0.872151 0.019991 0.892142 ( 0.892137)
Balanced: 0.617773 0.000000 0.617773 ( 0.617767)
Another benchmark checks how the internal algorithm which calculates new ranks performs. This method is still subject to optimization but one can see here that finding a rank between two close ranks takes significantly more time than finding a rank between two more different ranks.
Results (rank length of 100,000 letters):
Rehearsal ----------------------------------------------------------------------------
value between two close ranks: 0.872685 0.100091 0.972776 ( 0.992852)
value between two more different ranks: 0.000059 0.000006 0.000065 ( 0.000064)
------------------------------------------------------------------- total: 0.972841sec
user system total real
value between two close ranks: 0.818498 0.100112 0.918610 ( 0.928660)
value between two more different ranks: 0.000042 0.000000 0.000042 ( 0.000035)
- task to rebalance ranks
- method to output information about current balancing situation (number of ranked items, longest rank value, ...)
- ...
Contributing
Bug reports and pull requests are highly welcomed and appreciated. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.
- Fork the repository
- Create your feature branch by branching off of main (
git checkout -b my-new-feature) - Make your changes
- Make sure all tests run successfully (
bundle exec rake test) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create a new pull request
During development
- Install dependencies using
bundle install - Run all tests using
bundle exec rake test - Run a specific test using
m path_to_file:line - Run tests using a specific database adapter
DB=[sqlite,mysql,postgresql] bundle exec rake test
Setting up the different database adapter environments should be as simple as copying docker-compose.yml.example to docker-compose.yml and test/database.yml.example to test/database.yml and running docker-compose up -d.
Release a new version
- Update gem version in
Lexorank::Version - Add changelog entries
- Push changes to github
- Create a release on github and create a tag for the version (v0.1.0 for example).
- Build gem and push to rubygems.org
Lexorank is released under the MIT License.