Timeline for Update a column for every row of a large table to a unique value in a set range
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 24, 2016 at 10:57 | comment | added | Vladimir Baranov | @Andrew, I tried to guess what you mean by "ensuring suppliers products are not bunched together when randomising" and updated the answer with the second variant of the query. | |
| Mar 24, 2016 at 10:56 | history | edited | Vladimir Baranov | CC BY-SA 3.0 |
Added second variant
|
| Mar 24, 2016 at 10:00 | comment | added | Vladimir Baranov | I don't really understand what you mean by "supplier product bunching". My suggested query distributes evenly all rows of a table within the given 4 hour interval. This distribution treats all rows equally and doesn't depend on supplier at all. If you want distribution to depend somehow on the supplier and/or how many rows it has, please clarify the required logic in the question. | |
| Mar 24, 2016 at 9:24 | comment | added | Andrew | This now takes minutes and even though it doesn't directly address the potential supplier product bunching, the results are random enough for it to not really matter. Thanks for the excellent suggestion. | |
| Mar 24, 2016 at 9:21 | vote | accept | Andrew | ||
| Mar 23, 2016 at 11:32 | history | edited | Vladimir Baranov | CC BY-SA 3.0 |
Added a note about uniqueness of generated random values.
|
| Mar 23, 2016 at 11:22 | history | answered | Vladimir Baranov | CC BY-SA 3.0 |