Feature Request: Application-Time Periods
- Dominant language
- Go
- Stars
- 24.4k
- Forks
- 873
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 120
Description
MariaDB supports this feature that a potential customer uses:
https://mariadb.com/kb/en/application-time-periods/
Mariadb has it built in with application period constraints.
Postgres you can do the same thing fairly easily with btree gist https://stackoverflow.com/questions/62392003/postgres-best-way-to-avoid-overlapping-ranges-with-other-conditions
Mysql you have to do a bit annoying trigger: https://www.avaitla16.com/restricting-overlapping-time-periods-in-mysql
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no repository files, tests, or entry points. Start by reading the MariaDB application-time-periods reference and the linked PostgreSQL and MySQL approaches, then inspect Dolt's existing SQL constraint support. Done would require an agreed scope for application-time periods and corresponding behavior and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mariadb, mysql, postgresql, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100