4 ms·

Uh, "joint table" was the term used, not "table join". Pretty sure "joint table" in this context is referring to something like the intermediary table in a many

Uh, "joint table" was the term used, not "table join". Pretty sure "joint table" in this context is referring to something like the intermediary table in a many-many relationship, which I can see being quite intuitive to create without knowing this weird term that I've never heard of before, either.

qwertay 8y ago
I have always referred to it as a joining table
- TravelAndFood 8y ago
  Potayto potahto https://stackoverflow.com/questions/3045034/whats-the-correct-name-for-a-association-table-many-to-many-relationship https://stackoverflow.com/questions/3045034/whats-the-correc... I call BS if they "take points off" for not knowing the exact term "joint table", and if so that's not the kind of company I'd want to work for.
  - dorfsmay 8y ago
    You call BS on OP or the interviewer? Have you interviewed for a "unicorn" and other "cool" companies? Sadly, looking for excuses to rationalised that the interviewer doesn't like you is still a thing.
    - TravelAndFood 8y ago
      I call BS on the interviewer because as this thread and that question I linked on Stack Overflow demonstrates, "joint table" is not "the" term for the concept in question, and in fact there is no accepted one term. So, "marking down" for not knowing that term doesn't seem right. Edit: On the other hand, asking the question in a way that gets at the concept, not the term, seems very reasonable. I don't think it's relevant, but yes, I have interviewed at such companies.
geezerjay 8y ago
> Uh, "joint table" was the term used, not "table join". I don't believe OP is aware of the existence of table joins, and just reproduced what he thought was mentioned. Meanwhile, the DB operation he described is clearly a table join (create a new table by creating a relationship between two existing tables). That is also quite clearly a good reason for a prospective employer to lose interest in OP as a potential recruiter, and why his projects on Github fail to impress anyone. Portfolio projects only work in favor of a job applicant if they are any good, but if they are all a bunch of crap that is poorly put together and showcases incompetence, such as setting up a database system that tries to reinvent the wheel to fill in the gap of not knowing the very basics, then obviously that is disheartening to any potential recruiter.
- andrewflnr 8y ago
  What the hell else do you think they were doing with their "joint table" if not performing joins on it?

qwertay 8y ago

I have always referred to it as a joining table

TravelAndFood 8y ago
Potayto potahto https://stackoverflow.com/questions/3045034/whats-the-correct-name-for-a-association-table-many-to-many-relationship https://stackoverflow.com/questions/3045034/whats-the-correc... I call BS if they "take points off" for not knowing the exact term "joint table", and if so that's not the kind of company I'd want to work for.
- dorfsmay 8y ago
  You call BS on OP or the interviewer? Have you interviewed for a "unicorn" and other "cool" companies? Sadly, looking for excuses to rationalised that the interviewer doesn't like you is still a thing.
  - TravelAndFood 8y ago
    I call BS on the interviewer because as this thread and that question I linked on Stack Overflow demonstrates, "joint table" is not "the" term for the concept in question, and in fact there is no accepted one term. So, "marking down" for not knowing that term doesn't seem right. Edit: On the other hand, asking the question in a way that gets at the concept, not the term, seems very reasonable. I don't think it's relevant, but yes, I have interviewed at such companies.

geezerjay 8y ago

> Uh, "joint table" was the term used, not "table join". I don't believe OP is aware of the existence of table joins, and just reproduced what he thought was mentioned. Meanwhile, the DB operation he described is clearly a table join (create a new table by creating a relationship between two existing tables). That is also quite clearly a good reason for a prospective employer to lose interest in OP as a potential recruiter, and why his projects on Github fail to impress anyone. Portfolio projects only work in favor of a job applicant if they are any good, but if they are all a bunch of crap that is poorly put together and showcases incompetence, such as setting up a database system that tries to reinvent the wheel to fill in the gap of not knowing the very basics, then obviously that is disheartening to any potential recruiter.

andrewflnr 8y ago
What the hell else do you think they were doing with their "joint table" if not performing joins on it?