<FromGitter>
<sam0x17> I was trying it on .all which was wrong but it's actually on the model itself and on where chains I think
<FromGitter>
<sam0x17> what to do about min/max/average/sum though?
<FromGitter>
<Blacksmoke16> :shrug:
<FromGitter>
<sam0x17> I'm adding them -- might submit a pr
<FromGitter>
<Blacksmoke16> 👍
<FromGitter>
<sam0x17> I got it working for Granite::Querying however a little lost on how to do it on the actual query builder
<FromGitter>
<Blacksmoke16> be similar to `.count` no?
<FromGitter>
<sam0x17> more annoying because they have to have arguments , and count just calls assembler.count I guess I'll delve into whatever that assembler obejct is
<FromGitter>
<sam0x17> need this for a project like today but will see about a pull request later
<FromGitter>
<Blacksmoke16> kinda unfortunate that would return a `Float64 | Int64` tho?
<FromGitter>
<sam0x17> yeah, or I could do `sum` and `sum_f` or something
<FromGitter>
<Blacksmoke16> hm
<FromGitter>
<sam0x17> also not sure if `Symbol | String` is the idiomatic granite way of specifying a column name
<FromGitter>
<Blacksmoke16> is how things are typed in other places iirc
<FromGitter>
<sam0x17> cool
<FromGitter>
<Blacksmoke16> id rather get rid of symbols and use only strings, but :shrug:
<FromGitter>
<sam0x17> my argument is they are necessary unless there is some way of monkey patching additional values into an enum (which I don't think there is but maybe that does work haven't tried)
<FromGitter>
<sam0x17> and that's not a thing because the side effects would be bad so
<FromGitter>
<sam0x17> eh
<FromGitter>
<sam0x17> side note oh lol min and max should also support `Time`