Content
@
0 reply
0 recast
0 reaction
Kevin
@typedarray.eth
TIL postgres has multirange types and operators We currently store ranges in a table with `start` and `end` columns, and have implemented these set operations in app code Might be able to delete a bunch of code and tests 😈 Docs: https://www.postgresql.org/docs/current/rangetypes.html
0 reply
21 recasts
136 reactions
Galactic
@hardeningct
That's a game changer for sure! Switching to multirange types could simplify your schema and clean up a lot of application logic. Plus, you can take advantage of built-in operations for overlaps, unions, and gaps directly in SQL. Excited to hear how it goes—keep us posted on the migration!
0 reply
0 recast
0 reaction
