Ideas

[ankane]

Groupdate 6

• Raise error for non-attribute column argument without Arel.sql
• Return dates in SQL for day, week, month, quarter, and year - date_queries2 branch AND remove dates option
• Raise error for ranges with string bounds (.."2020-01-01" currently only includes first second of day, unlike ..Date.parse("2020-01-01") - alternatively, we could try to detect dates)
• Drop support for Active Record < 5.2 and Ruby < 2.6

Ideas

• Support endless ranges in range option - endless_range2 branch
• Support beginless ranges in range option

[jeffblake]

Thanks for the release! For fear of asking too much, do you mind merging master into group_by_duration?

[ankane]

np, merged

[nhh]

Is group_by_duration available on master? If so, are there any docs? Thanks!!

[ankane]

Hey @nhh, see #23 (comment) for the latest update.

[nhh]

@ankane thank you!

Whats the reason behind dropping "group_by_duration" in favor of steps "n".?

I really liked the group_by_duration method, because it feels "intuitive" and the ruby way. But reasons are probably technical, right?

[ankane]

@nhh I think it'll be less confusing for users. See #23 (comment).

[gekong]

I'm building a multi model chart by doing
model1.where('created_at < ?', Time.now).where('created_at > ?', Time.now - 14.days).group_by_day(:created_at).count
model2.where('created_at < ?', Time.now).where('created_at > ?', Time.now - 14.days).group_by_day(:created_at).count
the list created only lists each day that has a record and not the days that don't
is there a way to force this to show the count 0 on days that don't have any records? (this only happens in beginnings and endings)
I hope my explanation makes sense.

[gekong]

[ankane]

Hey @gekong, if you use the range option instead of where to limit the time range, it'll fill in zeros at the start and end.

[gekong]

Hey @gekong, if you use the range option instead of where to limit the time range, it'll fill in zeros at the start and end.

Awesome my bad!