User Events Management System
See original GitHub issueThis issue is required for the development of the issue on the bot repo https://github.com/python-discord/bot/issues/1172
The system will require two new tables: User Events
and Scheduled Events
User Events
Fields
- Name (primary key)
- Owner (user ID)
- Subscriptions (many-to-many field of users)
Operations
- Add a new event record
- Add a user to the subs field
- Query subs by name.
- Remove a user from the subs field
- Remove an event
Scheduled Events
Fields
- Event name (foreign key)
- Start time (datetime)
- Duration
Operations
- Add a new schedule for an event
- Query an event’s start time by name
- Remove an event’s schedule
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
What is an Event Management System?
An Event Management System (or Event Management Software) helps organizers plan, execute and report on events, driving success for their business.
Read more >Event Management Software
An event tech platform for face-to-face, online, and hybrid experiences. Are you using manual processes to plan and execute great events?
Read more >Best Event Management Software 2022 | Reviews of the ...
Event Management Software · Cvent Event Management · Webex Events (Formerly Socio) · monday marketer · Eventsquid · Swoogo · Bizzabo · HoneyBook...
Read more >9 Best Event Management Software That Will Make You ...
1. Eventbrite · 2. Whova (All-in-One Event Management Software) · 3. ConfTool · 4. Boomset · 5. Slack · 6. ProjectManager · 7....
Read more >Best Event Management Platforms in 2022
Top Event Management Platforms. Choose the right Event Management Platforms using real-time, up-to-date product reviews from 11045 verified user reviews.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, we could do that. Would require an extra field during creation probably. And a way to edit it.
What would be the reasoning behind changing an event name? If it’s just a typo at the moment of creation, they can just delete and make a new one. If it’s a matter of changing the purpose of the event, I’m not sure we want to allow that. The purpose of having an events table is to allow users to subscribe to them. Users who subscribe to an event about Yu-Gi-Oh! won’t want to suddenly find out they’re subscribed to an event about the Spice Girls.
Also, even if you use the UID the event name should still be unique. Design-wise, that sounds like it would be more fitting for it to be the primary key.