@billinkc I'm scared for life from that kind of naming convention. And ALL-CAPS to boot. I mean ALL-CAPS are for KEYWORDS as God Intended.

Morning

Morning

Morning

At first sight, I read: BiTelCHUS that was how they translated Bitleejuice here.

@bbaird Maybe they're Croatian? I had a lovely holiday near Krk once.

@JohnK.N. Only yesterday we encountered the CRLF-in-CSV problem and were able to fix it by using JSON files instead. I realise this may not be useful in your particular circumstance but posted an answer lest others may find solace in the future.

'Morning all.

@MichaelGreen Thanks.

Hi all, I've come across a strange problem with a DELETE in MariaDB - the second last code snippet works with MySQL 8 (and PostgreSQL), but not with any of the 4 versions of MariaDB on dbfiddle.uk...

Does anybody have any idea why? Is there some MariaDB weirdness with DELETEs?

@MichaelGreen I can accept Croatian Case

@Vérace Could you use this?

Sorry, this one dbfiddle.uk/…

Hi @McNets - fails on MariaDB 10.6, 10.5, 10.4 but works on MySQL. More MariaDB strangeness?

@Vérace it seems is not yet supported. jira.mariadb.org/browse/MDEV-22405

jira.mariadb.org/browse/MDEV-18511

@McNets - thanks for the heads-up about the CTE - strange... Anyway, got it!

@Vérace you don't need to use IN:

dbfiddle.uk/…

@ypercubeᵀᴹ - Thanks for your input! That's another solution... which one would be better? Is there a reason not to use IN(...)? I'll take a look at explain analyze...

@ypercubeᵀᴹ Hmmm... more and more interesting... The plan for your DELETE query is the shortest in MySQL. However, the query doesn't work at all in PostgreSQL... what would be the equivalent syntax in PostgreSQL?

@Vérace dbfiddle.uk/…

DELETE FROM t
USING u
WHERE t.x = u.x
...

The syntax for DELETE (and UPDATE) varies wildly from DBMS to DBMS when there are joins involved

Really does.

the above is similar to one of SQL Server's options. But that has 2 FROM

DELETE FROM t
FROM u
WHERE t.x = u.x
...

DELETE t FROM dbo.table1 AS t JOIN dbo.table2 AS u ON u.x = t.x; would be more SQL Servery

Or you could use MERGE.

MERGE t USING u ON u.x = t.x WHEN MATCHED THEN DELETE;

@PaulWhite that one is used by MySQL as well.

with the extension that we can delete from both tables

DELETE t,u FROM dbo.table1 AS t JOIN dbo.table2 AS u ON u.x = t.x;

Oh god

@ypercubeᵀᴹ y tho

why?

@ypercubeᵀᴹ Delete from both tables. Seems... bad.

hard eye roll

@ypercubeᵀᴹ Thanks for your input - really cleared up this (quite murky) topic for me!

@bbaird maybe someone wants to do cascade delete without declaring it with a FK

@ypercubeᵀᴹ If people want to do bad things they should have to type them out explicitly, like the good lord intended.

@bbaird it's the Wild West, You are just jealous that mysql has one gun than sql server so the users can shoot themselves ;)

@ypercubeᵀᴹ lol

The quality of Evan's trolling seems to have declined as of late

@bbaird mod abuse detected

@mustaccio Evan is quite emphatically not a troll. I mean look at his profile. Isn't that right, Evan?

@bbaird Didn't even last the hour! :-)

hi btw.

also, sorry to be such a killjoy @Evan

I mean, it would be a fun question in some other context