Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What's the best way to interact with timestamptz and tstzrange #9

Open
marchant opened this issue May 8, 2020 · 1 comment
Open

Comments

@marchant
Copy link

marchant commented May 8, 2020

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!

@volkanunsal
Copy link
Owner

Would cast be enough?

Yes, I use casting pretty extensively.

Should these types be added to your project?

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants