SQLBolt – Interactive lessons and exercises to learn SQL
81–87 of 87 posts
Re: SQLBolt – Interactive lessons and exercises to learn SQL
#82Earlier quoted context omitted.
We are trying to revive the art in our shop. Just got done building a really clean 3NF model for our problem domain and we are in the process of moving 100% of our custom configuration needs to SQL queries. From a biz strategy perspective, we can scale up a lot faster if all we need to do is find people who know (or can be taught) SQL. Consider the amount of time it would take to ramp someone on 1 SQL schema vs the e…
This is great if you have highly-connected client apps. Its not as doable when you can't guarantee connectivity. In those cases, you need to ship/duplicate business logic to the clients to work around the network issues. Its a hard problem.
Re: SQLBolt – Interactive lessons and exercises to learn SQL
#83I'm of the firm opinion that you can have a very successful career purely as an SQL genie.
I feel fairly confident that I can write SQL queries for basically any result set (On a well designed DB). But the project I am working on is close to breaking me (VERY bad DB design, in progress) Also: I think knowing your way around triggers and such is quite important too though. I should learn them properly some day.
I've had the displeasure of working with databases with triggers that fire other triggers, and all that logic should've been moved into the application itself. They're a powerful tool to have in your toolbox, but should be used sparingly, and should be kept as simple as possible.
Re: SQLBolt – Interactive lessons and exercises to learn SQL
#84Re: SQLBolt – Interactive lessons and exercises to learn SQL
#85Re: SQLBolt – Interactive lessons and exercises to learn SQL
#86Fun tutorial! Some form of autocomplete would be nice.
Re: SQLBolt – Interactive lessons and exercises to learn SQL
#87Earlier quoted context omitted.
Yeah, sure, you can always write raw SQL queries, but that has nothing to do with your ORM, does it? I was talking about ORMs in general, not about the programmer in particular. So yes, you are right that if you have enough engineering resources you can support everything. But most ORMs don't help you with this, so it is not a feature of ORMs. You can always bypass it though. The comparison with JS doesn't fit realy…
When GP says 'you can use the advanced features', 'you' refers to the person developing the ORM, not to a developer using the ORM. So the ORM author can do the hard work of allowing advanced features to work across databases. And it's transparent to the developer using the ORM.