(public).sospep.subjects ~ view article ~ sql-reference

<h1 style="text-align: center;">COLLECTION - SQL - best-of-2016</h1>
<h2>[WHAT]</h2>
<ol>
<li>] by Don Sagrott, founder @ sospep.com - a collection of&nbsp;of articles related to learning and using SQL.&nbsp;</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>]&nbsp;</li>
</ol>
<h2>[WHERE]&nbsp;</h2>
<ol>
<li><strong>] READ THE FULL ARTICLE</strong></li>
<ol>
<li>] see the EXAMPLE section below -&nbsp;</li>
</ol></ol>
<h2>[WHEN]</h2>
<ol>
<li>] 2017-04-13</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li><strong>[x]&nbsp;<a href="http://www.sohamkamani.com/blog/2016/07/07/a-beginners-guide-to-sql/" target="_blank">A beginners guide to thinking in&nbsp;SQL</a></strong></li>
<ol>
<li>] by - __ - explaining some of the basic of using SQL to query a database for data.</li>
</ol>
<li><strong>[x]&nbsp;<a href="http://www.craigkerstiens.com/2016/01/08/writing-better-sql/" target="_blank">Writing more legible&nbsp;SQL</a>&nbsp;</strong></li>
<ol>
<li>] by Craig Kerstiens - A number of times in a crowd I&rsquo;ve asked how many people enjoy writing SQL, and often there&rsquo;s a person or two. The follow up is how many people enjoy reading other people&rsquo;s SQL and that&rsquo;s unanimously 0. The reason for this is that so many people write bad SQL. It&rsquo;s not that it doesn&rsquo;t do the job, it&rsquo;s just that people don&rsquo;t tend to treat SQL the same as other languages and don&rsquo;t follow strong code formatting guidelines. So, of course here&rsquo;s some of my own recommendations on how to make SQL more readable.</li>
</ol>
<li><strong>[2016-10-09]&nbsp;<a href="http://www.sqlstyle.guide/" target="_blank">SQL&nbsp;style guide</a>&nbsp;(+257)&nbsp;<a href="https://news.ycombinator.com/item?id=12671667" target="_blank">comments</a>&nbsp;(#146)</strong></li>
<ol>
<li>] Do's and Dont's for database design, includes db naming convention guidelines for db's, table names, feildnames, etc</li>
</ol>
<li><strong>[2016-04-25]&nbsp;<a href="https://blog.jooq.org/2016/04/25/10-sql-tricks-that-you-didnt-think-were-possible/" target="_blank">SQL&nbsp;Tricks</a>&nbsp;(+182)&nbsp;<a href="https://news.ycombinator.com/item?id=11570348" target="_blank">comments</a>&nbsp;(#41)</strong></li>
<ol>
<li>] by Lucas Eder - 10 SQL tricks you didnt think were possible - aka some cool stuff here that is available in most oss RDBMS (except mysql) ] everything is a table, ] data generation with recursive sql, ] running total calculations, ] finding the largest series with no gaps, ] ...</li>
</ol>
<li><strong>[x]&nbsp;<a href="https://news.ycombinator.com/item?id=13417326" target="_blank">Ask HN: What is the best online resource to learn advanced&nbsp;SQL?</a>&nbsp;</strong></li>
<ol>
<li>*] <strong><span style="text-decoration: underline;">you</span></strong> can mine the comments section of this post to get a wealth of top notch SQL resources including ...&nbsp;</li>
<li>] EXAMPLE - <a href="http://use-the-index-luke.com/sql/preface" target="_blank">http://use-the-index-luke.com/sql/preface</a>&nbsp;</li>
</ol>
<li><strong>[x]&nbsp;<a href="http://wozniak.ca/what-orms-have-taught-me-just-learn-sql" target="_blank">What ORMs have taught me: just learn&nbsp;SQL&nbsp;(2014)</a></strong></li>
<ol>
<li>] byGeoff Wozniak - &nbsp;I've come to the conclusion that, for me, ORMs are more detriment than benefit. In short, they can be used to nicely augment working with SQL in a program, but they should not replace it.&nbsp;</li>
<li>]&nbsp;I've found myself thinking about the database as just another data type that has an API: the queries. &nbsp;The queries return values of some type, which are represented as some object in the program. By moving away from thinking of the objects in my application as something to be stored in a database (the raison d'&ecirc;tre for ORMs) and instead thinking of the database as a (large and complex) data type, I've found working with a database from an application to be much simpler. And wondering why I didn't see it earlier.</li>
<li>]&nbsp;Regardless of whether I find that stored procedures aren't actually that evil or whether I keep using templated SQL, I do know one thing: I won't fall into the "ORMs make it easy" trap. They are an acceptable way to represent a data definition, but a poor way to write queries and a bad way to store object state. If you're using an RDBMS, bite the bullet and learn SQL.</li>
</ol>
<li><strong>[]&nbsp;<a href="http://beets.io/blog/sqlite-performance.html" target="_blank">We&rsquo;re pretty happy with&nbsp;SQLite and not urgently interested in a fancier DBMS</a>&nbsp;-&nbsp;</strong></li>
<ol>
<li>] by @beets - developer explains why in the case of his application, staying with a simple easy to use flatfile database like SQLite is better than moving to a full fledged RDBMs.</li>
</ol>
<li><strong>[2017-02-11] <a href="https://www.brentozar.com/archive/2013/02/7-things-developers-should-know-about-sql-server/" target="_blank">7 things developers should know about SQL Server</a>&nbsp;</strong></li>
<ol>
<li>] by Brent Ozar - Ozar an industry consultant, offers up a handful of tips for use with msfts mssql rbdms including don't use ORDER BY&nbsp;</li>
</ol></ol>
<h2>[HOW-TO]</h2>
<ol>
<li>]</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>] # 7228 -&nbsp;<a href="/view/task?id=7228" target="_blank">CREATE-article# 5686</a> (this)&nbsp;</li>
<li>] SRC = HN.algolia?='sql', &nbsp;</li>
</ol>
<h2>[RELATED]</h2>
<div><ol>
<li>] += writing modern sql&nbsp;</li>
<li>] <a href="/view/books?id=60" target="_blank">technology-developer-db</a> - library containing books related to RDBMS/SQL development/usage</li>
</ol></div>
<div>&nbsp;</div>

~ view article ~ Chapter] index FROM [ Book] research IN [ libraries] technology-developer-db