News for hackers. Stuff that matters.
Re:Your database skills are not 'good to have' by rhdunn on Monday April 01, 2024 @10:58AM (#39894796)
Doesn't that happen when you use a highly normalized database table design, though where you create tables to avoid repeating data? Or if you have a lot of 1/many to many relationships in mapping tables. I.e. you'll end up with a lot of tables you need to join on to collate that data (authors, subjects, languages, etc.) to display to the user.

You could break the joins into three parts:

1. searching/filtering -- which tables you need to join on to match the selected queries;

2. sorting -- determining which column(s) of data to sort the results by; and

3. displaying -- which tables you need to join on to retrieve the information needed to display the information to the user.

These may be different or have overlaps.

Re:Your database skills are not 'good to have' by stouset on Monday April 01, 2024 @11:03AM (#39894870)
I think they’re saying that JOINing over three or four tables is really just not that big a deal for most situations, particularly if you have the needed indices.
Re:Your database skills are not 'good to have' by rhdunn on Monday April 01, 2024 @11:09AM (#39894940)
Yeah. That's something you would expect databases to be good at. Expecially as normalization and many-to-many relationships make multiple JOINs common, which was my point.
Re:Your database skills are not 'good to have' by ergonaught on Monday April 01, 2024 @11:05AM (#39894908)
Joins are rarely the problem. See the sigh.