The simplest way to group by:
- day
- week
- hour of the day
- and more (complete list below)
🎉 Time zones supported!! the best part
🍰 Get the entire series - the other best part
Works with Rails 3.1+
Supports PostgreSQL and MySQL, plus arrays and hashes
💘 Goes hand in hand with Chartkick
User.group_by_day(:created_at).count
# {
# 2013-04-16 00:00:00 UTC => 50,
# 2013-04-17 00:00:00 UTC => 100,
# 2013-04-18 00:00:00 UTC => 34
# }
Results are returned in ascending order by default, so no need to sort.
You can group by:
- second
- minute
- hour
- day
- week
- month
- quarter
- year
and
- hour_of_day
- day_of_week (Sunday = 0, Monday = 1, etc)
- day_of_month
- month_of_year
Use it anywhere you can use group
.
The default time zone is Time.zone
. Change this with:
Groupdate.time_zone = "Pacific Time (US & Canada)"
or
User.group_by_week(:created_at, time_zone: "Pacific Time (US & Canada)").count
# {
# 2013-03-10 00:00:00 PST => 70,
# 2013-03-17 00:00:00 PDT => 54,
# 2013-03-24 00:00:00 PDT => 80
# }
Time zone objects also work.
Weeks start on Sunday by default. Change this with:
Groupdate.week_start = :mon # first three letters of day
or
User.group_by_week(:created_at, week_start: :mon).count
You can change the hour days start with:
Groupdate.day_start = 2 # 2 am - 2 am
or
User.group_by_day(:created_at, day_start: 2).count
To get a specific time range, use:
User.group_by_day(:created_at, range: 2.weeks.ago.midnight..Time.now).count
To get the most recent time periods, use:
User.group_by_week(:created_at, last: 8).count # last 8 weeks
To exclude the current period, use:
User.group_by_week(:created_at, last: 8, current: false).count
You can order in descending order with:
User.group_by_day(:created_at).reverse_order.count
or
User.group_by_day(:created_at).order("day desc").count
To get keys as date objects instead of time objects, use:
User.group_by_day(:created_at, dates: true).count
# {
# 2013-03-10 => 70,
# 2013-03-17 => 54,
# 2013-03-24 => 80
# }
or make this the default with:
Groupdate.dates = true
To get keys in a different format, use:
User.group_by_month(:created_at, format: "%b %Y").count
# {
# "Jan 2015" => 10
# "Feb 2015" => 12
# }
or
User.group_by_hour_of_day(:created_at, format: "%-l %P").count
# {
# "12 am" => 15,
# "1 am" => 11
# ...
# }
Takes a String
, which is passed to strftime, or a Symbol
, which is looked up by I18n.localize
in i18n
scope 'time.formats', or a Proc
. You can pass a locale with the locale
option.
User.group_by_period(:day, :created_at).count
Limit groupings with the permit
option.
User.group_by_period(params[:period], :created_at, permit: %w[day week]).count
Raises an ArgumentError
for unpermitted periods.
users.group_by_day { |u| u.created_at } # or group_by_day(&:created_at)
Supports the same options as above
users.group_by_day(time_zone: time_zone) { |u| u.created_at }
Count
Hash[ users.group_by_day { |u| u.created_at }.map { |k, v| [k, v.size] } ]
Add this line to your application’s Gemfile:
gem 'groupdate'
Time zone support must be installed on the server.
mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root mysql
or copy and paste these statements into a SQL console.
Groupdate 2.0 brings a number a great improvements. Here are two things to be aware of:
- the entire series is returned by default
ActiveSupport::TimeWithZone
keys are now returned for every database adapter - adapters previously returnedTime
orString
keys
View the changelog
Groupdate follows Semantic Versioning
Everyone is encouraged to help improve this project. Here are a few ways you can help:
- Report bugs
- Fix bugs and submit pull requests
- Write, clarify, or fix documentation
- Suggest or add new features