Requirements
Each league/tournament/etc allocates sequences of game numbers to each schedule - Rich : ok
Game numbers are only unique within each schedule and may be reused in other schedules - Rich : ok
Game numbers often have a prefix and suffix to identify which league and category - Rich : ok
A schedule with groups/flights will have a sequences per group (flight 1 will have 1000-1999, flight 2 will have 2000-2999, etc within the same U13 schedule) - Rich : ok
Draft games can have their numbers re-sorted based on the date/time prior to publishing, but published games cannot be re-sorted - Rich : ok
Renumbering is a manual action. Automatically doing so may cause confusion as people use numbers as a reference while scheduling, so it’s usually only done in preparation for publishing
| Infotip |
|---|
from Richard : Could you describe the meaning of : groups/flights do you mean pool/section within the same category (schedule) Seb : Yes group = flight = pool = section = conference |
Currently we have a (published) games table and a drafts table, where drafts essentially act as isolated containers of a schedule.
When creating a (published) game directly, if you do not specify a game number, it defaults to the system ID (which is a standard incrementing postgres sequence). Otherwise the game number specified is used as is.
When creating drafts, you must specify a starting game number, which will automatically increment within the draft, with an option to re-number the games (sorted by date). The draft’s starting game number option only exists within the draft, and ceases to exist once the draft is published.
When publishing the draft, if a draft game matches the game number of a published game, the published game will be updated instead of creating a new game.
| Warning |
|---|
Rich : This way of doing is questionnable, before i read the Proposed behaviour. |
Proposed behaviour
Following the implementation of SPR-453 Draft Redesign, two game tables will exist: Game (published) and DraftGame (unpublished). The original Draft table that creates an isolated container effect will no longer continue to exist. Sequences (this proposal) are necessary to introduce to maintain the original start number draft option functionality.
...