Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
sunfishcc4445270dWhat SQL is this? How many are tables using these 2?
helloworld8923270dI’m no database expert by any stretch, but why the hell would you have the table with just the name in it if there are only two tables, surely there is no need for a relationship. one table would suffice?
arekxv942269dUsing strings as foreign keys is a really bad choice performance wise but if its a table which will have a small amount of rows (like less than 1000) from now and forever, then that is not a big deal. On the other hand. I think its dumb to use two tables to represent a parent-child relationship. They do know that a table can refer to itself? 😃
coopaaaah63269d@arekxv I'm sure they do. In some cases the parent will be very small, but the child table it's referencing certainly won't.
The project is about managing batch jobs. In this scenario, the parent here would be a app, and the child is the batch that ran for that app. With how they've designed it, a row would be created for each batch that's run for said app.
The state of said batch is also managed in that table. I tried to expand it out and say this would not preform well, especially for the UI,but I couldn't get anywhere with them.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job