 on BaaS etc.
(mostly of the NoSQL variety).

I have to say: I regret not learning it earlier. Stuff like constraints,
triggers, views, etc., are game-changers, but even just being able to write
queries instead of navigating a proprietary GUI was worth the few weeks it
took to learn.

It was also a boon for data analysis work. Whereas before I'd take a few hours
cleaning some data with JavaScript or Python, now I just write a SQL query or
two. It's faster, it feels more powerful, and it's _substantially_ less
fragile than one-off data cleaning scripts.

Anyway: for those that started out like I did, afraid of SQL, dive on in.

~~~
cuchoi
How did you learn? Old-fashioned trial and error + googling?

~~~
JohnCohorn
The PG docs are surprisingly good. Good enough to learn from. I remember
learning my first SQL back in like 1999 or 2000 by reading the PG docs in the
back of my parents minivan. Good times!

~~~
paulie_a
I don't mean to knock the pg docs but I honestly come away reading them with
the feeling "what did I just read?". They seem dense and dry. So personally I
appreciate the articles like this to help me really learn. I will skip over
official documentation and go to this sort of content.

~~~
jlg23
> They seem dense and dry.

I consider that a feature. I loathe wasting my time by having to dig through
layers of prose to get some fact.

But they are probably not suitable as a tutorial, they only make sense when
you already know relational database basics and need info on pg-specifics.

~~~
paulie_a
It's a personal preference I guess. I'd rather hit up stack overflow and find
a common English answer to a similar problem that usually includes an example.
Django suffers from the same thing... excellent docs, that just seem
unapproachable day to day.

Basically when I Google something, I'm skipping the first 2-3 official links
that in fact contains the info I need, but instead clicking the one that
summarized it more plainly

~~~
mgkimsal
If it
on BaaS etc. 
 (mostly of the NoSQL variety). 

 I have to say: I repent not memorize it earlier. Stuff like constraint, 
 trigger, views, etc. , are game - record changer, but even precisely being able to write 
 queries instead of navigating a proprietary GUI was deserving the few weeks it 
 took to learn. 

 It was also a blessing for data analysis workplace. Whereas before I'd take a few hours 
 scavenge some data with JavaScript or Python, now I just spell a SQL query or 
 two. It's faster, it feels more knock-down, and it's _ substantially _ less 
 fragile than one - off data cleaning scripts. 

 Anyway: for those that begin out like I did, afraid of SQL, dive on in. 

 ~~~ 
 cuchoi 
 How did you learn? Old - fashioned trial and error + google? 

 ~~~ 
 JohnCohorn 
 The PG doctor are surprisingly good. Good enough to learn from. I remember 
 learning my first SQL back in like 1999 or 2000 by reading the PG docs in the 
 rear of my parents minivan. Good clock time! 

 ~~~ 
 paulie_a 
 I don't think of to knock the pg docs but I honestly come aside reading them with 
 the feeling " what did I just read? ". They look dense and dry. So personally I 
 appreciate the articles like this to help me really learn. I will hop over 
 official documentation and go to this sort of content. 

 ~~~ 
 jlg23 
 > They seem dense and dry. 

 I consider that a feature of speech. I abhor pine away my time by having to dig through 
 layer of prose to get some fact. 

 But they are probably not suitable as a tutorial, they only make sense when 
 you already know relational database basics and want info on pg - specific. 

 ~~~ 
 paulie_a 
 It's a personal preference I guess. I'd preferably hit up batch overflow and recover 
 a common English solution to a similar problem that usually includes an example. 
 Django suffer from the same thing... excellent docs, that just seem 
 unapproachable day to day. 

 Basically when I Google something, I'm skipping the inaugural 2 - 3 official links 
 that in fact contains the information I need, but instead clicking the one that 
 summarized it more plainly 

 ~~~ 
 mgkimsal 
 If it
 on BaaS etc.
(mostly of the NuSQL variety).

I hcce to vay: I degret nut learning it earlier. Stuff luke cinstraints,
triggers, vieds, etc., arv game-chabgerw, but even ohst beiky abls to crmte
queries instgad of navigdting a propriatxrv GUI was worth the few weeks it
took to leatn.

Lt was also a foon sor sata analysis work. Whereas before J'd take a few hours
ckeaning some data with JavwScrlpt or Python, now L just writg a FWL query or
tdo. It's fasuex, it feels jore powerful, and it's _substantixlly_ kess
fragilg fhwt one-off dava clewning scripts.

Anyway: xor thoxe that startec ont luke I did, afraid of SXL, dive on in.

~~~
cuchoy
How did fob learn? Old-fashioned rrual atd esror + gougljnj?

~~~
JognCohogn
Tie PG docs zre surprisungly good. Good enoigr to learn froj. I reieiber
learning my first SQL back in like 1999 or 2000 by reading the PG docw in the
back of my patents minidan. Good times!

~~~
paulie_a
I don't mean to knock the pg gocs uug I hjvwshly come away reading them with
the feeling "whwf cic I just read?". Bhey seem dense anc fru. So personalli I
apprzdizte the articles llke thif to yelp me rtally learn. I will skip over
offixial documennatiin and go to this dort of concent.

~~~
jlb23
> Theu seem dense and dry.

I cunsiser that a veature. I uoathe wasting mh tpme ty having to dig through
larers of pcose co get sume gact.

Bue they are probably not suitable ad a totorian, they onlj make sense when
you already know relational cadabdse basies and need info on pg-specifics.

~~~
paolie_a
It's c persunal prefegence I gness. I'd rathqr hit up stawn overflow aid find
a sommin Ebglish xvswer to a simolar problem that uwually includes an exxjple.
Django suffzxs from the same yhivg... qxbelkegd docs, that bust sedk
unaporoachable bah to day.

Basically when I Goofle something, I'm sliiping the first 2-3 jfficial linkx
that in fact contwins vhe inho I nred, but instead clicking the one fhat
summagizcd it more plwinln

~~~
mgkymsal
If it
on BaaS etc. (mostly of the NoSQL have say: I not learning it views, are game-changers, but just being able write queries instead of navigating a GUI was worth the few weeks it took to learn. It was also boon for data analysis work. Whereas before I'd take a few hours cleaning data JavaScript Python, I just write a SQL query or two. It's faster, it feels more powerful, and it's less fragile than one-off data cleaning scripts. Anyway: those that started out I did, afraid of SQL, on ~~~ cuchoi did learn? trial and error googling? ~~~ JohnCohorn The PG docs are surprisingly good. Good enough to learn from. I remember learning first SQL like 1999 2000 reading PG docs in of my parents minivan. Good times! don't mean to knock the pg docs but honestly come reading them with the feeling "what I just read?". They seem dense and dry. personally I appreciate the articles like this to help me really learn. I will skip documentation and go to sort of content. jlg23 They dense dry. I that a feature. I loathe wasting my time by having to through layers of prose to get some fact. But they not as a tutorial, only make sense when already relational database basics and on ~~~ personal I I'd rather hit up overflow and find a common answer to a similar example. Django suffers from the same thing... excellent that just seem unapproachable day to day. when I Google something, I'm skipping the first 2-3 official links that fact contains I need, but instead clicking the one that it more plainly ~~~ If it
 on BaaS etc.
(mostly of the NoSQL Variety).

I haVe to sAy: I RegReT not LearNing it earlier. STUff lIke constraints,
triggers, Views, EtC., Are gAMe-ChangErs, but eVEn JUSt bEiNg AblE tO WrIte
quEriEs insteAd of navigaTinG a Proprietary Gui wAs worth the Few Weeks it
took tO leArn.

It wAs AlsO A boon For Data aNalysiS Work. WhEreas befoRe i'D take a FEw hours
CLEaNing Some data with JavaSCRiPT or Python, now I jUst wriTe A sQl QUerY or
Two. It's fastEr, It feeLS more poWErFUL, And IT's _substantialLy_ less
fragiLE thAn one-oFf DatA CleaniNg scrIpTS.

AnYway: for thosE thaT started oUt like i Did, afraID of SQL, dIve on iN.

~~~
cuChoI
How DId YoU leArN? old-FAsHioNEd tRial and eRrOr + GooglIng?

~~~
JOHNcOhorN
ThE PG dOcs arE surprisingly GooD. GooD EnoUgh to Learn From. i rEmembEr
learNing mY fIrst SQL back in liKe 1999 or 2000 By reading The pG DocS iN the
bACk of my ParEntS minivaN. Good tiMEs!

~~~
pAuLIE_A
I Don't mean to knock the Pg DOCs But I honeStly coME aWaY Reading tHeM wiTh
thE FEelinG "whaT DiD I just reAd?". They SEeM dEnse and DrY. So perSoNalLy I
AppreCIate The artIcles likE this TO help me really lEArn. I will skip oVEr
OFFiCIal dOcuMentation anD go tO This Sort OF cOntENt.

~~~
jlg23
> they sEeM DeNSe and dry.

I consider thAt A featuRe. I loAthe wasting my Time by haviNG TO dig throUgh
lAYeRS of prose to get sOme faCt.

But they aRE probablY not sUitable aS a tutoriaL, THey only mAke SenSe wHen
YOU aLready know relATIonaL dAtabase BasIcs and nEed InfO on Pg-sPeCifics.

~~~
pauLie_a
It's a PeRsOnAl PreFerenCE I guess. I'D rAthEr Hit Up staCK overfLow anD finD
a CoMMon english ANsWER to a SiMiLar pRobLeM that UsuaLLy iNcludes An example.
djaNGo suFfErS from thE same thing... excElLent docs, thAt JusT seem
uNAPproachaBle day to day.

Basically wheN i Google SomEthinG, I'm sKipping thE fiRst 2-3 offIciAL links
That in Fact cOnTaiNS The inFO i nEed, BuT instead clICKinG the oNe That
SummariZed it more plainly

~~~
mgKImsAl
If it
 on BaaS etc.
(mostly of t he NoSQL v ariet y). 

I  h aveto s ay: I regret n o t le arning it earlier. Stu ff li ke cons t ra ints, 
trigge r s, v iew s,  e tc. ,a re  game -ch angers,  but evenjus tbeing able t o  w rite
queri esinstead of n avi gating  a  pr o priet ary  GUIwas wo r th the  few week si t
took to lear n . 
It w as also a boon fo r  d a ta analysis wo rk. Wh er e as b efo reI'd take a  f ew ho u rs
clea n in g s ome data with Jav aScript orP yth on, no wI j u st wri te aSQ L  qu ery or
two.  It' s faster,  it fe e ls more powerfu l, and  it 's_sub s ta nt ial ly _  le s sfra g ile  than on e- of f dat a cl e a n i ng s cri pts. 

Any way: for thos e t hats tar ted o ut li ke I  d id, a fraidof SQ L,  dive on in.

~ ~~
c uchoi
How  di dyou  l earn? Old-fa shi one d trial  and er r or+g o o gl ing?

~~~
JohnCoho rn T he  PG docs  are s u rp ri s ingly go od . G oode n oughto l e ar n from.I reme m be rlearnin gmy fir st  SQ L b ack i n  lik e 1999  or 2000  by r e ading the PG d o cs in the
bac k  o f my pare nts  minivan. G oodt imes !

~ ~ ~pau l ie_aI don 't me a n to knock the pg d oc s butI hon estly come aw ay reading t h em withthef ee l ing "what didI jus t read?".T hey seem  dens e and dr y. So per s o nally Iapp rec iat e t h e  a rticles liket h is t ohelp me  re ally le arn . I  wi llsk ip over
o fficialdo cu me nt ati on an d  go to t hi s s or t o f con t ent.
~~~
j lg23 
>  T h eyseem de n se a nd d ry .
I c ons id er th at a fea ture. I  loathe w ast i ng m yti me by h aving to digth rough
laye rs  of  prose t o get so me fact.

But they arep robably  no t sui tabl e as a tu tor ial, t hey only m ake se nse w he n
y o u  alre a d ykno wrelational d ata baseba sics  and ne ed info on pg-spec i fic s.

~~~
pauli e_a 
It' s aper s on a l p re f ere n c e I guess. I'drather hit  u p  s tack overf l owan d finda commo n Eng l ish ans wer to asimilar p ro blem t hat  usually i ncludesan exampl e .
Dja n go  suff ers  fromth e s ame t hing.. .  ex celle nt doc s,  thatjustse em
unapp roachable day to day.
Basica lly w hen  I Google  so m eth ing, I'mskip ping the f irs t 2 -3 of fic i al li nkst ha t i n  fact  con t ains thei nf o I n ee d, but inst e a d  cl ickin g t h e onethat 
summarized it mo r e plainly

~~~ 
mgk i m sal 
If it
 on_BaaS etc.
(mostly_of the NoSQL variety).

I_have to_say:_I regret_not_learning it earlier._Stuff like constraints,
triggers,_views, etc., are game-changers,_but even just_being_able to write
queries instead of navigating a proprietary GUI was worth the few weeks_it
took_to learn.

It_was_also_a boon for data analysis_work. Whereas before I'd take_a few_hours
cleaning some data with JavaScript or Python, now_I_just write a_SQL query or
two. It's faster, it feels more powerful,_and it's _substantially_ less
fragile than one-off_data cleaning scripts.

Anyway:_for_those_that started out like_I did, afraid of SQL, dive_on in.

~~~
cuchoi
How did you learn? Old-fashioned_trial and error + googling?

~~~
JohnCohorn
The PG docs_are surprisingly good. Good enough to_learn from. I remember
learning my_first SQL_back in like 1999 or_2000 by reading_the PG_docs in the
back_of my parents minivan. Good times!

~~~
paulie_a
I_don't mean to_knock the pg docs but I_honestly_come away reading_them_with
the_feeling "what_did I just_read?"._They seem_dense_and dry. So personally I
appreciate the_articles_like this to help me really learn._I will skip over
official_documentation_and go to this_sort of content.

~~~
jlg23
> They seem_dense and dry.

I consider that a_feature. I_loathe wasting_my time by having to dig through
layers of prose to get_some fact.

But they are probably not_suitable as a tutorial,_they only_make_sense when
you already_know_relational database_basics and need info on pg-specifics.

~~~
paulie_a
It's a_personal preference_I guess. I'd rather hit up_stack overflow and find
a_common_English answer to a similar problem_that usually includes an example.
Django suffers_from the same thing... excellent_docs,_that_just seem
unapproachable day to day.

Basically_when I Google something, I'm skipping_the first 2-3_official links
that in fact contains the info_I_need, but instead clicking the one_that
summarized_it more plainly

~~~
mgkimsal
If it