« first day (5166 days earlier)   

01:32
@SeanGallardy can confirm that worked. Crazy that they'd just foist unwanted CoPilot crap on their customers for more money without asking. That should be illegal.
If only that were the case with many things foisted upon us...
 
5 hours later…
06:46
Only available on đť•Ź for the moment
> base table bythe same key
FFS
Fixed
It had a red squiggle and everything
Last minute edits FTW
Why does everything I try to do recently immediately reveal some long-standing issue
You’re looking in the right places
Had to happen eventually
Like a dandy little Poirot
> this means Instead of
Missed the random cap on first read
07:09
Good spot. Fixed
Have you changed your mind about join alias ordering?
> ON E.id = B.id;
No, that's the way I've always written them
Huh
I thought you had said you prefer the opposite in here somewhat recently
I have had it set that way for years in SQLPrompt
Jun 12, 2024 at 20:50, by Paul White
X join Y on Y.a = X.a has much better logical flow
@ErikReasonableRatesDarling I think that's the conversation you're referencing
07:27
I came to the same conclusion yesterday.
I don’t know how much you care or it matters, but tue second merge is missing the serializable hint included in the first one
07:46
@ErikReasonableRatesDarling There's no need for serializable isolation in that example
I only use hints where they are needed, not as magic dust
@ErikReasonableRatesDarling Thanks for confirming
 
3 hours later…
10:41
@PaulWhite Interestingly, WHEN MATCHED THEN DELETE correctly transforms it to an inner join dbfiddle.uk/kqxBsuRV
DELETE of a joined view/CTE is allowed on MERGE, even though it's not allowed on a normal DELETE, as I've noted elsewhere
5
Q: Merge Delete on joined tables is allowed but has a bug

CharliefaceTo start off, an updatable CTE, derived table or view may be the target of an UPDATE directly, even if it has multiple base tables, as long as all columns are from the same source table. But they cannot be the target of a DELETE, even if columns from only one table are selected. Msg 4405 Level 16...

Hmmm actually that fiddle is deleting from the wrong table, due to this bug. Flipping the join into a right-join gets the correct table, and doesn't fail, but adds a weird Segment-Sequence-Filter for some reason.
 
1 hour later…
12:12
Wordle 1,347 6/6*

⬛⬛⬛⬛🟨
⬛🟩🟨⬛🟨
⬛🟩🟨🟩🟩
🟩🟩⬛🟩🟩
🟩🟩⬛🟩🟩
🟩🟩🟩🟩🟩
 
1 hour later…
13:30
@PaulWhite you put this as a dupe, but none of the answers on the linked answers are correct for this scenario. Would it make sense to transfer my answer over and keep it as a dupe or undupify it? dba.stackexchange.com/questions/345403/…
Hmmm seems to depend which column you join on. If you explicitly join Extended.id table then it transforms to inner-join, if you join on Base.id then you still get the error even for the THEN DELETE because it keeps the right-join dbfiddle.uk/MijADflQ
Note in both cases it's attempting to write to Extended not Base.
@SeanGallardy What's your take on my bug report on the above feedback.azure.com/d365community/idea/…
13:51
Wordle 1,347 4/6*

⬛⬛⬛⬛⬛
🟩🟩⬛⬛🟨
🟩🟩🟨⬛⬛
🟩🟩🟩🟩🟩
14:02
@Charlieface It looks nice, love the font selection
wow, that price increase was really just for co-pilot
but the good news is that it is included in the price increase
Is that good news, though?
@SeanGallardy Aside from the styling... what about the actual bug?
i suppose it's better than paying for something and not getting it
like a vending machine on the fritz
just waiting for that payday to drop
@SeanGallardy Yes of course, imagine all those people having to actually add it on manually, why not have MS do it for you?
14:06
@Charlieface No idea, I try to stay far away from query stuff
I'm not a QO/QE fan
even ES not really a fan
sean only breaks hearts and availability groups
Used to be some utility companies would put T.O.L. (trying our luck) on your bill.
what.gif
may have been a joke idk
deadpan
Oh, I wouldn't put it past utility companies though - that's some straight up stuff they'd do
14:09
i'd send it back with T.O.T.O.T.
trying out tons of tannerite
Anything that gets special designations to constantly screw you while forcing you to use their crap product is already scammy, so it tracks
well electricity is a pretty good product i think
14:24
Forcing me to a provider and then allowing them to willy nilly charge for things is not. It's why I checked the codes for requirements on hooking up to local power, which isn't always a requirement.
I'll be my own electricity provider
starting your own coal plant?
Something like that
well at the very least i hope you get a decent bbq out of it
I use pellets these days, put it on a timer and walk away
oh dear
apparently one drive hadn't opened since november of last year
cpu fans on red alert
14:29
That and Teams are the first things I uninstall
i sometimes need to use onedrive as an alternative clipboard
🥴
Truly the end times are near
god i hope so
enough is enough
> -2 The row fetched is missing.
that seems bad
Is it missing missing or just misplaced? Do we need to call the police?
> INFO Completed parsing. Parsed 8008 build files in 117.26s.
maybe your nickname should be titters
14:44
@Charlieface That's expected. The whole basis of the issue is that the MATCH finds a row, then the UPDATE clause attempts to update it. Problem is, they're rows from different tables. The first row does exist, the second is the result of the outer join; it's not a real row. See my đť•Ź artcile.
paul đť•Źpects you to read and comprehend
@SeanGallardy Yeah the 'dupe' system is often not perfect. Your answer is the answer to his specific (arguably off-topic) question, thanks to debugging efforts in comments. The dupe target was suggested by another user. On balance, I think it is a useful signpost to that more general Q & A. I don't think it would make sense to merge the Q & As because they're not exact duplicates. Your answer would look strange on the other question. I'm open to changing things if people feel strongly about it.

« first day (5166 days earlier)