Skip to content

Locations Supertype Table, Related Tables, and Location Subtype Tables - #136

Open
Norberttony wants to merge 9 commits into
mainfrom
Norbert_K_121_Locations
Open

Norberttony wants to merge 9 commits into
mainfrom
Norbert_K_121_Locations

Conversation

@Norberttony

Copy link
Copy Markdown
Contributor
  • Added location supertype with all of its related tables and all of its subtypes.
  • Changed buildings table to be a subtype of locations
  • Moved update logging mixin from Building to Location
  • Added a LOSSY db migration (never run with real user data) where the downgrade might not actually work lol

@DJFreer92
DJFreer92 marked this pull request as ready for review October 27, 2026 02:25
@DJFreer92
DJFreer92 requested review from a team as code owners October 27, 2026 02:25
@DJFreer92
DJFreer92 enabled auto-merge (squash) October 27, 2026 02:25

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the enum should have int values to reduce data redundancy in the database

from backend.schema.special_operating_hours import SpecialOperatingHours


class Location(UpdateLoggingMixin, Base):

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this can use the ID mixin

@DJFreer92
DJFreer92 requested a review from a team October 27, 2026 03:12

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Locations is probably too broad for a single feature

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

API/DB - Create Locations Tables, Services, and API Routes

2 participants