We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Users will want to store duration data in columns. We should allow them to do so and implement this type appropriately in the backend.
We should support a duration type in Mathesar and allow users to use it. Postgres has a built in type for this – INTERVAL, so we'll use that.
INTERVAL
Tasks that need to completed:
Related issues and PRs:
Also see Postgres "Date/Time Types" docs.
The text was updated successfully, but these errors were encountered:
I'm closing this issue since the one pending item #432 is tracked separately.
Sorry, something went wrong.
No branches or pull requests
Problem
Users will want to store duration data in columns. We should allow them to do so and implement this type appropriately in the backend.
Proposed solution
We should support a duration type in Mathesar and allow users to use it. Postgres has a built in type for this –
INTERVAL
, so we'll use that.Tasks that need to completed:
INTERVAL
type in the backend #430Additional context
Related issues and PRs:
Also see Postgres "Date/Time Types" docs.
The text was updated successfully, but these errors were encountered: