I’ve been working on an implementation this morning my time (UTC+10) and have been following the same approach. I should have something you can hack on in a few hours. I’m also going to define a custom composite type option that serialises resolution and metadata along with the tstzrange/tstzmultirange.
kip
ex_cldr Core Team
kip
ex_cldr Core Team
Ha, well, it was on my list but I was thinking that no one would ask for that for a while. And then you asked…
I’ve published tempo version 0.3.0 that addresses all the issues you raised (I think).
And there’s an experimental Ecto integration library you can try out at GitHub - kipcole9/tempo_sql: Ecto types for Tempo and Postgres · GitHub. It has ecto types for native tstzrange and tstzmultirange types with a :resolution parameter which will truncate the loaded data to the desired resolution.
It also has custom composite types which build on the native types but also preserve resolution and metadata. I think those would be my preference noting they will take more space.
There are tests, but it needs more exercising before its ready for hex release.
1
nathanl
mudasobwa
Creator of Cure
I have a fancy idea of utilizing the fact that macros know whether they were called in :match context, and provide a dedicated implementation for that particular case.
That said, one can actually do ~TEMPO[2026Y] to match any interval fitting within 2026, and so forth. Even more, that version might accept modifiers, so that ~TEMPO[2026Y]MD would match anything happened in 2026 and expose month and day local variables to the scope.
@kip if you are interested in this feature, let me know, I’ll provide a PR:
1
kip
ex_cldr Core Team
I’m not really sure I understand the intent or problem space yet, but any time @mudasobwa has an idea I’d be crazy to not accept a contribution and see where it goes! Anything is possible in releases < 1.0.
2
mudasobwa
Creator of Cure
mudasobwa
Creator of Cure
kip
ex_cldr Core Team
Great work @mudasobwa, thanks very much. A great addition. Just have to work out why we have a locale setup mismatch (which is what is causing the formatting errors). I’ve made a comment in the PR.
Thanks again, will be part of the next published release.
1
mudasobwa
Creator of Cure