Timeline for Ignore duplicate rows in a join - and take only one of them
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 11, 2023 at 6:36 | vote | accept | Ade | ||
| Sep 9, 2023 at 13:00 | comment | added | J.D. | @Vérace heh, good to see other mobile users. I'm always answering from my phone too. | |
| Sep 9, 2023 at 7:34 | comment | added | Vérace |
@Steve on my mobile phone - gotcha! I use my tablet on the bus sometimes and that's bad enough! +1
|
|
| Sep 9, 2023 at 5:19 | comment | added | Steve | @Vérace, agreed, as I say I didn't write the majority of the code shown - it was copied from the OP's original, and then surgically altered (on my mobile phone) to show the nested query and remove less relevant parts of the outer query. The code example itself was a last-minute addition to the answer, as I wasn't sure I'd made the arrangement of code elements, and the concept of a nested query, sufficiently clear in words alone. Finally, I'm not a MySql user, so I'm not in a position to know offhand which syntactic elements are correct or necessary there. | |
| Sep 9, 2023 at 3:00 | comment | added | Vérace | Should be some aliasing also and remove backticks! :-) | |
| Sep 8, 2023 at 19:25 | comment | added | Steve | @ErgestBasha, agreed, it was just a mangled copy and paste from the OP's original. | |
| Sep 8, 2023 at 19:24 | comment | added | Ergest Basha | Parenthesis are excess on the on condition, beside that I agree with your answer | |
| S Sep 8, 2023 at 19:21 | review | First answers | |||
| Sep 8, 2023 at 21:40 | |||||
| S Sep 8, 2023 at 19:21 | history | answered | Steve | CC BY-SA 4.0 |