Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mastering PostgreSQL in Application Development

masteringpostgresql.com

Post reply on HN
Print view View original

21–30 of 101 posts

Re: Mastering PostgreSQL in Application Development

#23

Post by Xorlev »

spacemanmatt wrote: post #16
alpos wrote: post #5

Earlier quoted context omitted.

Best not to sneak an email collection scheme in on people even if it really is only for your newsletter. Most people have more than enough spam in their inbox already, if someone wants to get updates it's very easy for them to just click a button that says "Click here to get updates".

Email for updates being a foot in the door for further communications is pro forma and legally regulated. I think you're unnecessarily suspicious.

Even if it isn't nefarious, it's often unwanted. I usually turn around if I have to provide my email to see some sort of whitepaper or sample because it means I will have to later unsubscribe from whatever email list I was put on and hope they don't share the list with others (which happens, often).

Re: Mastering PostgreSQL in Application Development

#24

Post by davidcuddeback »

virtuexru wrote: post #21

This book seems like an amazing resource however I definitely cannot afford the price tag at $179 unfortunately. :(

I was a bit surprised by that as well. If you scroll further down the page, there are less expensive options. The eBook is $39. Paperback is $49.

Re: Mastering PostgreSQL in Application Development

#25

Post by craigkerstiens »

qaq wrote: post #18
craigkerstiens wrote: post #8

As someone that cares greatly about the Postgres ecosystem there aren't nearly enough books out there, so really excited to see this one come to life. Instead of targeting DBAs the focus on app devs is very refreshing so that people can start to leverage more of the awesome in Postgres. I haven't yet read the book myself but absolutely will. If you're curious to read some of Dimitri's writing ahead of time his blog i…

I think it's to a degree a function of significant volume of high quality material available in the open. It's hard to sell a book when you can go to Bruce Momjian's site https://momjian.us and get access to a ton of information and that is just one resource.

Agreed there are a number of pieces out there in the open, but not many in a consolidated form or that flow from one step to the next. Perhaps it is because there are a number that blog about all things Postgres, but a really common question I hear from people is what book should I pick up if I want to become an expert at Postgres. And while some books are out there, there hasn't been a perfect answer to date, hoping this one helps :)

Re: Mastering PostgreSQL in Application Development

#26

Post by jonstaab »

I've been wondering for a while about the practicalities of using postgres as a replacement or near-replacement for a traditional backend - does anyone have any opinions on how far it's wise to go with this (postgres-only? authentication? direct connections from the client?) and/or how feasible that kind of thing is?

Re: Mastering PostgreSQL in Application Development

#28

Post by odammit »

The “dead tree edition.” Good play, sirs.

I’m going have to get that one though. I can’t seem to focus/finish when reading educational books on my kindle or in PDF form.

I like the “turn thousands of lines of code into queries”... I can’t count the number of times I’ve seen application code doing something a query could do either to appease an ORM or because a backend engineer wasn’t fluent in intermediate SQL.

Re: Mastering PostgreSQL in Application Development

#29

Post by scriptkiddy »

_joel wrote: post #17

I don't know how much cross-browser testing you do, but the site looks completely broken in Firefox, renders fine on Chrome. EDIT, I tried adding https to check (cert is wrong too, however) and it looks better. Be aware the link posted (for some reason) is HTTP only.

Hmm. Firefox 56.0 running on Ubuntu 16.04 and it's working fine minus the hijacked scroll. Note to all front end developers: STOP HIJACKING SCROLL! It's bad UX. No exceptions.
Post reply on HN