which fiddle are you referring to?
How can we use where condition in this fiddle and if data is not available for particler date or this where condition then show blank data on that date
Finally on db<>fiddle, thanks @ypercubeᵀᴹ
can you give us a bit more details? Like is this mysql, mssql or something else? I'd personally like to see your attempts as well
3. Given a transactions table as below, find out the count of users who transacted for the first time on a Monday Transaction_ID User_ID Transaction_Date Amount
Yeah, not being verbose is something I should definitely train. OK, will keep in mind for the future. I appreciate your feedback, thanks.
It *is* very long. It would have been easier for me to consume in two parts, I think. But I don't speak for everyone :) That being said, I think your explanations are clear and the whole thing flows well.
Hahaha this really made me laugh :D
Thanks, Josh! Is it hard reading? Once I've written it, I realized that probably it is quite long (it was even longer with logical trees included, which were thrown out at some revision). I was thinking to split it in two parts, but now it's as it is.
```xml <WaitStats> <Wait WaitType="JOSH_TO_READ_MY_POST_IN_DEPTH" WaitTimeMs="Infinite" WaitCount="1" /> </WaitStats> ``` :D
Just got around to reading it in depth - fantastic stuff! So neat to see how those predicates are removed at different stages (i.e., simplification vs earlier compilation / constant folding activity).
::: quote 1 115032 70ac1a052b69788b840dc7af631544ba35aa71997240f3a4b5b0b7f57bc166a4 219,219,219 131,133,133 Josh Darnell replying to i-one *— 5 days ago* *in [The Tavern](/meta?room=1#c115032)* >Awesome :D I am looking forward to it! :::
Sorry about that, pretty much all the Linux machines were affected when I added MariaDB 10.6 and ran out of space in my ZFS pool (which I need to keep an eye on going forward)
MySQL, MariaDB, Oracle seem to be failing as well. SQL Server 2019 seemed to work for me (the version test at least) but not SQL Server 2019 for Linux.
dbfiddle doesn't seem to work with Postgres any more. If I call e.g. https://dbfiddle.uk/?rdbms=postgres_13 and then click the "Run" button, it results in "Run failed"
for the transcript though: if you've arrived here from GlobalSign internal documentation, you are morally obligated to @-reply/ping me from this message ![blob](/image?hash=9281c078b714ebed1d91068e852139218bb4738546b82428b935e482717d8008)
i wonder if anyone will ever follow it :-P
Haha that's a lovely circular reference.
in a pleasing (possibly ironic) symmetry, the link in that screencap is actually to the chat message in this room where i started rubber-ducking :sweat_smile:
...but it's the explanation I put in the documentation I did for it ¯\\\_(ツ)_/¯ ![blob](/image?hash=2e179e8867756fa56cf6b16502b25eee3f44c24fc6e1275469b84786ddf8d762)
my working theory is this: because there's a single element in the `row()` returned by `jsonb_array_elements()`, then `->>` gets lazily assigned. `with ordinality` adds a second element to the `row()` returned and forces the error. sadly this isn't supported by my attempt at a repro... <>https://dbfiddle.uk/?rdbms=postgres_10&fiddle=02994ab816288a1f0aba1287ab299d21