I have never used and will (in the foreseeable future) not use SQL.
I already have a ton of stuff on my plate that I need or want to learn, SQL is not one of them and I won't include it "just because". Right now it's absolutely useless to my skillset and not something that I have an interest with either. This might change, and then we'll see, but right now it's not even a thought.
I'm pretty unhappy with my current job, but at least I can say I'm not expected to use my very limited and rusty knowledge of SQL. Working with relational databases is one of the least fun aspects of programming I've ever encountered. If a job interview heavily stresses SQL knowledge, I'm probably not a good fit for the position. Even if the position itself demands less SQL ability than the interview suggests, I take the questions as an implicit requirement for success. Also, if I end up in an interview where they delve more deeply into SQL than "when would you use and inner vs outer join", I've probably failed somewhere in screening for jobs I should interview for.
I have never used and will (in the foreseeable future) not use SQL.
I already have a ton of stuff on my plate that I need or want to learn, SQL is not one of them and I won't include it "just because". Right now it's absolutely useless to my skillset and not something that I have an interest with either. This might change, and then we'll see, but right now it's not even a thought.