I’m not talking full blown ORM here, not a fan of those either. I’m talking about some light weight wrapper that basically just assembles SQL statements for you, while giving you just a little more type safety and automatic protection against SQL injection, and not sacrificing any performance. I’m coming from the JVM world, where Jooq and Exposed are examples of that kind of thing.
As the other commenter said, the Jetbrains IDEs do this perfectly fine. Although I’d also argue that if you’re working with SQL from within another language already, a DSL wrapper is probably gonna be the better way to go about this.
Well then use all-caps keywords whenever working on those systems, I don’t care. But an edge case like that shouldn’t dictate the default for everyone else who doesn’t have to work on that, that’s all I’m saying.
My ide isn’t limited to color when it comes to highlighting, so being color blind generally shouldn’t be a problem. Set keywords to underlined, bold, italic, whatever works for you.
Your other examples I can see, but at least at my work those are rare edge cases, and I’d rather optimize for the brunt of the work than for those. Of course at other places those might be much more of a concern.
I understand it as an attempt to get very basic, manual syntax highlighting. If all you have is white text on black background, then I do see the value of making keywords easy to spot by putting them in all caps. And this probably made sense back when SQL was first developed, but it’s 2023, any dev / data scientist not using a tool that gives you syntax highlighting seriously needs to get with the times
Actually, no. “Legitimate interest” has a specific legal meaning under GDPR, and has to clear a way higher bar than just wanting to make money and always be weighed against the affected person’s interests as well.
It’s when it’s in a company’s best interest to measure this data.
That is not correct, or at least it’s incomplete. You make it sound like only the company’s interest matters, but it always has to always take into account the interests of the data subject as well, and if the two are at odds, you need to make a judgment on how to balance those.
Storing IP addresses for example falls into this - there is a legitimate interest of the company to keep its IT systems protected, and to do that effectively, storing IP addresses is necessary. This interest weighs pretty highly, and since the expected effect on the subject is minimal and there’s no less invasive way to achieve the same result, it’s okay to do without a way for the user to opt out.
Error tracking, is already a little more tricky - you need to have a good argument why you actually need the personal data to effectively find and fix issues, because most of the time, there’s ways to do that without processing personal data just as effectively (beyond the IP address of course being used when sending error reports).
Of course this is all just theory, and in practice, companies will often try to get away with way more liberal interpretations of what constitutes legitimate interest. My point is that legitimate interest as a concept is not the problem, and is actually necessary for the whole thing to work. The problem is companies bending the law and not properly being regulated.
I wouldn’t expect such a sharp dropp-off at the end of it again though, even if it was temporary black-out or something, I’d expect there to be more of a trail
Oh, that sounds really cool! At what time does this validation happen? While you code, or later at build time?