globocom / globocom/database-as-a-service
team vs database constraints
Open
enhancement
- Dominant language
- Python
- Stars
- 371
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
- teams cannot have all users removed if there is at least one database associated
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are identified in the issue. Trace how teams, users, and associated databases are represented and where team membership removal is handled. Done means a team with an associated database cannot have its final user removed, with coverage for that constraint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100