Post

Reasons why SELECT * is bad for SQL performance: An old blog (with Oracle-specific examples) with a whole range of reasons why. It's not only about network traffic and SQL plan execution, but client side processing and memory usage as well. tanelpoder.com/posts/reason...

13/3/26, 3:18 am5 reposts21 likes

Jon Stone

@socialmediahandle.bsky.social

13 Mar

Dont they say, "never do that" at school?. I would think this would simply get rejected on most decently configured production db. Like it would bounce back and tell your manager?

Tanel Poder

@tanelpoder.com

13 Mar

Yeah, I once proposed a database "strict mode" configuration parameter when talking to Oracle development folks, which would simply reject (with an ORA- error) or log a warning about any bad practices it sees in App-DB interaction (like directly comparing VARCHAR2 to a NUMBER bind var datatype etc).

Quade

@quade2.bsky.social

13 Mar

Aren't there security implications too?

oscar

@kureal.bsky.social

13 Mar

interesting - knew a few of these, but there's many more that I didn't lol

Tanel Poder

@tanelpoder.com

13 Mar

Yeah, I ended up getting deeper into the rabbit-hole myself (regarding cursor mem usage, etc) when writing that blog post!