search

pep-dortmund / member-database

Our member database application
Other
9 stars 1 forks source link

Status relationship #153

Closed maxnoe closed 2 years ago

maxnoe commented 2 years ago

This renames status to status_name and adds a relationship called status for EventRegistration.

This enables a dropdown menu for the registration status in the admin interface that can be used to manage events (e.g. moving people from the waitinglist to confirmed or cancel a registration).

status

codecov-commenter commented 2 years ago

Codecov Report

Merging #153 (099b281) into master (7eb561d) will increase coverage by 0.02%. The diff coverage is 58.33%.

@@            Coverage Diff             @@
##           master     #153      +/-   ##
==========================================
+ Coverage   75.42%   75.45%   +0.02%     
==========================================
  Files          23       23              
  Lines         997      998       +1     
==========================================
+ Hits          752      753       +1     
  Misses        245      245
Impacted Files Coverage Δ
member_database/events/__init__.py 61.05% <50.00%> (ø)
member_database/events/models.py 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 7eb561d...099b281. Read the comment docs.

maxnoe commented 2 years ago

@The-Ludwig is was needed to make it work with postgresql... I need to check again why this was there at all, since the table was created with unique constrained already in the beginning

maxnoe commented 2 years ago

Ok, I am now sure it's not needed. Still not sure why it was there but the unique constrained is still there after all the migrations.