New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Initial Outfit DB structure #1179

Open

Resaec wants to merge 1 commit into master from outfit_db_structure

Contributor

Resaec commented Mar 3, 2024

This migration (presumably) allows for the storage of all outfit relevant data (except titles).

Outfit

each outfit has one entry in the outfit table
each name is unique
ranks are inlined (static 1:n, join unnecessary)
faction is limited to 0,1,2,3
decal is limited to 1 through 26 (inclusive)

OutfitMember

each avatar can at most be a member in one outfit
each outfit can only have one rank 1 (leader) member
rank is limited to 1 through 8 (inclusive)
there is a "quick access" index on outfit and avatar for rank 1 (leader)

OutfitPoint

each (outfit, avatar) combination can only exist once
a (outfit, NULL) combination can not be limited yet (not a big deal)
points is limited to >= 0
deleating a avatar will have his points remain as (outfit, NULL)


          Initial Outfit DB structure

be7e7a3

Contributor Author

Resaec commented Jul 29, 2024 •

edited

Loading

OutfitMember and OutfitPoint should both get a created timestamp to indicate date of creation.
OutfitPoint should allow negative point counts as there is a gm command to add/substract points.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet