Yeah I mean it’s definitely possible to write a mostly sensible string-number equality function that only breaks in edge-cases, but at this point it’s all kinda vibes-based mush, and the real question is like… Why would you want to do that? What are you really trying to achieve?

The most likely case is that it’s a novice that doesn’t understand what they’re doing and the Python setup you describe does a better job at setting up guardrails.

I don’t really see the connection to concatenation, that’s kind of its own thing.

Not quite. As the previous commenter said, every string has at least one string representation (i.e. 100 -> “100”, “1e2”). So there’s no sensible way to write a pure function handling that, you’re just cooked no matter what you do.

Amazing.

What are your thoughts on the 1999 War in Dagestan?

Lucky guess, I guess.

Not sure how you managed that but im at a hotel anyway.

I want to cyberbully her

Diabolical

Woketangle is covering up the fifth side

Because he’s a politician and he understands that his rhetoric has to ramp up slowly to convince his audience. Go to your local pub/bar and say that to someone that isn’t a terminally online ML, see how they react.

Commie-site keys??? LIBERAL!!! GUT IT!

Nah, they are supposed to be unique. If it was that it’d at least be a design choice potentially worthy of criticism. But consider, who’s more likely to have fucked up a database task: Musk? Or the designer, someone with a degree (a real degree) on this topic?

Don’t worry: since he’s so big on transparency, I’m sure he’ll release the schema so we can check his work… 🙄

Sounds like he got confused looking at a view of a join.

SELECT holder_name, amount
FROM account JOIN transaction ON transaction.account_id=account.id;

-- WTF!! THERE'S DUPLICATES!!!

real 😭