Skip to main content
9 events
when toggle format what by license comment
Oct 29, 2020 at 13:15 vote accept Aridez
Oct 28, 2020 at 6:51 answer added Gordan Bobić timeline score: 2
Oct 28, 2020 at 3:44 comment added Aridez @davidbak I misworded that. It's just dropping one join from the current query. There are other benefits coming from the framework I'm using that would end up making the code more readable, hopefully this clears things up a bit more.
Oct 28, 2020 at 3:44 comment added Aridez @1201ProgramAlarm I considered this because, once set, this data should never change. The code that sets this values exists only in one place also.
Oct 28, 2020 at 0:59 comment added davidbak To add to my previous comment: With SQL databases you do best to think in terms of sets of data - union, intersect, project - and then you get the best results! (You can google for tips on how to do this.)
Oct 28, 2020 at 0:58 comment added davidbak I'm not sure I understand "drop one join query" - unless you're suggesting that the six boldfaced queries you've listed are currently being implemented as a six separate database requests with corresponding round-trips? If that's the case: keep working with the current schema until you get your request down to one actual query. You can have more than one two-table join in a single query! You should be able to join all those tables on the appropriate fields with the appropriate conditions and then just let the database do its work with one round-trip.
Oct 28, 2020 at 0:43 comment added 1201ProgramAlarm Have you measured the performance of the two approaches? And considered the additional development headaches maintaining all that redundant, copied data will entail including fixing the inevitable bugs when they get out of synch?
Oct 28, 2020 at 0:25 review First posts
Nov 11, 2020 at 0:25
Oct 28, 2020 at 0:22 history asked Aridez CC BY-SA 4.0