Closed heydoyouknowme0 closed 1 month ago
Wouldn't you want to initialise the hostels schema into master first, and then rebase sample-db
onto master
?
Wait, no. Put the overview and stuff into the schema. The data being improbable to change is no reason to not put it in there. Please don't use that as a criterion.
Rebase sample-db
on master
and add sample data in that branch
I messed up. didnt realize employeeId is a varchar, it links properly inside studio but doesn't actually fetch when I try to fetch using the relation(which i realized when rebasing hostels page).
two many to one relation between same table dont work unless I use two different ids to do so
Edit: employee id seems to be int in actual data just changing that might also work
As a lesson, always test your changes before moving the PR out of a draft
There was no indication of an error anywhere even after pushing to the db ˙◠˙
also what should I do now we can either make employee id an integer or another multi table relation(like staff)
Um, that relation looks wrong though. Why is an employeeId being linked to a hostel id? Even if we made the datatypes match, why would they logically ever match?
uhhh, Im sorry everything's broken I'm stupid
rest data improbable to change so left in i18n