151–160 of 185 posts
The overall mantra of this book is: Don't reimplement database features in your application that the dbms can do for you. I really strongly agree with this, and even if you don't recall any of the concrete recipes in this book then this mantra will hopefully stick.
Earlier quoted context omitted.
You don't value your time = free Other people do value their time, therefore it's not free for them.
Yes "nothing is free" yet we still often call these things free. It definitely wasn't free for him to make it. Average person on here views those hours as billable if they were to do it themselves, when they make decisions about what to do, or alternatives (opportunity cost). Maybe he should charge them consulting rates for this PDF (and not take their -- correction: an -- email. The horror). It's only because this i…
A person gives you a whole book they wrote for free and you're complaining about asking for an email? WTF
It's not exactly free if they're asking something in return.
Earlier quoted context omitted.
Yeah, I was sad seeing some of the reactions. To each his own. For a student like me, I would gladly take a free resource and won't mind the newsletter. Maybe OP can also put a donate button for people who don't want to provide their E-Mail and get the book. Thanks a lot, tpetry!
The criticism is that it's not honest. "For free" is not correct. It's "book against harvesting your contact data". If that's what the first page would say, then it would be honest and nobody would be upset. But acting as if it's been "published" out of pure altruism is just misleading people, and they are righfully pointing that out.
While it does look really handy and well put together, unfortunately none of the tips in the book that I read before giving up are useful to someone using mssql
I also can't C&P from your pages as they're images, but Ghost Conditions Against Unindexed Columns has '... AND type = in (3, 6, 11)' - is that right or did you mean 'type in (...)'. It also talks about multi-col indexes as being more useful in some cases, true, but very elementary.
This is good and well done, but please don't oversell it.
Earlier quoted context omitted.
Can you recommend some resources to achieve (b)? Just basic stuff without going full guru on every little detail. Or do you just mean using indexes basically? I'm just not sure how many unknown unknowns I have wrt sql.
The gist is: 1. Trace your application, so you know which query is running slowly in production. 2. Using this exact query, run `EXPLAIN ANALYZE` or whatever your RDBMS equivalent is. 3. Read the output, see which step is taking the slowest. Use google to help. 4. Google-fu until you find out which index might help you. Over time, (3) and (4) requires less and less Google, because there's really only a few common cas…
Earlier quoted context omitted.
The criticism is that it's not honest. "For free" is not correct. It's "book against harvesting your contact data". If that's what the first page would say, then it would be honest and nobody would be upset. But acting as if it's been "published" out of pure altruism is just misleading people, and they are righfully pointing that out.
Would you pay money in lieu of providing your real email address? If so, how much?