You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for sharing this, I'm looking at using it, storing event's rule in a column of my event's table. I've decided to use timestamptz to store utc time as well as tstzrange for an event's time range, all stored as UTC in the database. What would be your suggestion to use your project, which as far as I can tell expects timestamp so far. Would cast be enough? Should these types be added to your project? If yes and you can guide me through it, happy to give it a shot as I integrate and use it. Thanks!
The text was updated successfully, but these errors were encountered:
I don't think it's necessary to add a new type for all different time values. The syntax and behavior of defining new types changed somewhat in recent versions of postgres. I haven't had chance to keep up with it.
First of all, thanks for sharing this, I'm looking at using it, storing event's rule in a column of my event's table. I've decided to use timestamptz to store utc time as well as tstzrange for an event's time range, all stored as UTC in the database. What would be your suggestion to use your project, which as far as I can tell expects timestamp so far. Would cast be enough? Should these types be added to your project? If yes and you can guide me through it, happy to give it a shot as I integrate and use it. Thanks!
The text was updated successfully, but these errors were encountered: