Timeline for DISTINCT not reducing two equal values to one
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7, 2023 at 14:52 | vote | accept | jimbobmcgee | ||
| Aug 4, 2023 at 18:30 | comment | added | jimbobmcgee | In any case, binary-collating the column is more than sufficient for this case -- I was more surprised that there was a property of equality that was being applied in WHERE that was not being applied in DISTINCT, GROUP BY, etc. | |
| Aug 4, 2023 at 18:22 | comment | added | jimbobmcgee | The affected types aren't ones that are documented other than "for internal use" anyway though. -- INSERT/SELECT cares not for your "internal use" :-) | |
| Aug 4, 2023 at 18:20 | comment | added | jimbobmcgee | So I'm unclear if the entire rows will be duplicated or not in the event that these spin locks are encountered -- I encountered it originally when I was trying to INSERT/SELECT into a history table where I had made name part of the PK. I figured I would aggregate with SUM/GROUP BY name and it still happened, so I reduced it to the most straightforward example (i.e. SELECT DISTINCT) | |
| Aug 4, 2023 at 13:59 | history | edited | Paul White♦ | CC BY-SA 4.0 | deleted 49 characters in body |
| Aug 4, 2023 at 13:38 | history | edited | Martin Smith | CC BY-SA 4.0 | added 267 characters in body |
| Aug 4, 2023 at 13:31 | history | edited | Martin Smith | CC BY-SA 4.0 | added 105 characters in body |
| Aug 4, 2023 at 13:25 | history | edited | Martin Smith | CC BY-SA 4.0 | added 596 characters in body |
| Aug 4, 2023 at 8:02 | history | edited | Martin Smith | CC BY-SA 4.0 | added 495 characters in body |
| Aug 3, 2023 at 15:44 | history | answered | Martin Smith | CC BY-SA 4.0 |