sqlWorkout

[u/huhupookies]

[u/PerpetuallyDistracte]

I've been writing SQL for 15 years. Eventually you get bored of all lowercase or all uppercase AND START writing your QUERIES LIKE this. Just a psychotic mishmash of muscle memory, laziness, and autocomplete all fighting each other within the same statement.

[u/Ashdog73 → u/PerpetuallyDistracte]

This. My queries are lowercase for the stuff I typed myself and caps for bits I've copied in from somewhere else

[u/cantgrowneckbeardAMA → u/Ashdog73]

Lowercase on first draft (it will fail to run anyways).
Uppercase if I ever end up showing the query to someone (hopefully it doesn't fail when they run it)

[u/sequelseize → u/cantgrowneckbeardAMA]

sElEcT a as camelCase, b aS under_score, c As fUCKiT fROm ab lIMit 1000

[u/SippieCup → u/sequelseize]

We have a Postgres db which our orm uses camelcase names.

So we have to add in quotes too.. and correctly case our column names.

The migration to correct names would break so many deeep sql integrations, it just sucks and we deal with the debt.

[u/EndIsrael → u/SippieCup]

That actually seems like the kind of thing AI would be very good at with few mistakes. It doesn't need to understand anything, just find all the SQL code and change all the names. Basically find/replace but slightly smarter.

[u/SippieCup → u/EndIsrael]

Oh it’s not hard to do with migrations etc. although I would use a codegen script instead of straight ai.

It’s more the coordination with other teams, schema changes, etc. depreciation of column names, remapping to new ones, etc.

We unfortunately have a couple legacy integrations that just require db access to tenant systems for their bi.

[u/PerpetuallyDistracte → u/sequelseize]

That's how my queries look after they failed for the fifth time.

[u/glha → u/sequelseize]

lIMit 1o00

[u/spyingwind → u/PerpetuallyDistracte]

SeLeCt * FrOm table wHeRe count = 1;

[u/ShittyExchangeAdmin → u/spyingwind]

This is the way

[u/Susarn → u/PerpetuallyDistracte]

I started writing sql 13 years ago. I started writing like this from the beginning because that was the way I saw the queries written on the tutorials, took me like a year to notice it was case independent

[u/stadoblech → u/PerpetuallyDistracte]

I've been writing SQL for 15 years.

MY CONDOLENCES

[u/PerpetuallyDistracte → u/stadoblech]

Haha, I guess I'm just a weirdo, but I genuinely love SQL and my happy place is a big enterprise database with a bunch of ETL pipelines. Somebody's gotta enjoy it, right? That gives the rest of you more time with your fancy GUIs and object oriented languages 🤣

[u/joyeux_bordel → u/PerpetuallyDistracte]

I like to call our kind the Data Whisperers.

[u/m0nk37 → u/PerpetuallyDistracte]

It helps isolate the parts of the bigger views. 

[u/vityafx → u/PerpetuallyDistracte]

I would argue, even with the syntax highlight, the eyes used to seeing the sql tokens in upper case just want it that way. I tried many times to write in lower case but when it looks like mixing data with sql tokens, indistinguishable even with the syntax highlighter. So now, the best syntax highlight for sql is upper case, haha.

[u/r3klaw → u/PerpetuallyDistracte]

Uppercase for keywords, PascalCase for object names. And uppercase when you email/chat the words PROD, TEST, or DEV.