Just FYI, in the "The Dead Tree Edition" section, "professionally" is spelled wrong: A professionnally printed paperback of 332 pages, with the same content.
Maybe it’s the first edition of the website :D
Mastering PostgreSQL in Application Development
31–40 of 101 posts
Re: Mastering PostgreSQL in Application Development
#32Thanks for putting the time and effort into this, Dimitri
Re: Mastering PostgreSQL in Application Development
#33I 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.
I'm also seeing broken/missing CSS on Debian/FF 56.0.2.
Re: Mastering PostgreSQL in Application Development
#34As 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…
"focus on app devs"
This is exactly the type of book I've been wanting for a long time.
Re: Mastering PostgreSQL in Application Development
#35I'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?
Derek Sivers wrote in 2015 about merging more of the business logic into postgres, including generating JSON in postgres [0]. I've personally used this approach and found it quite powerful. There may be downsides to that approach if somebody else is going to be maintaining the project and doesn't understand postgres too well.
There's also PostgREST[1], which exposes a REST API to a postgres database and has been discussed on HN before [2,3]
[0] https://sivers.org/pg [1] https://postgrest.com/en/v4.3/ [2] https://news.ycombinator.com/item?id=13959156 [3] https://news.ycombinator.com/item?id=9927771
Re: Mastering PostgreSQL in Application Development
#36I 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.
I'm also seeing broken/missing CSS on Debian/FF 56.0.2.
Yep, that would tally, I'm on Ubuntu 17.10
Re: Mastering PostgreSQL in Application Development
#37As 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.
Thanks for sharing the link to Momjian’s blog. I enjoyed reading his posts for content and his concise writing style.
Re: Mastering PostgreSQL in Application Development
#38I'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?
I haven't put anything into production yet but I've been playing with PostGraphQL (https://github.com/postgraphql/postgraphql). It automatically creates a GraphQL endpoint based on your schema using Node. You define your application logic as functions in your schema. It also can handle authentication for you. I'd definitely recommend checking it out.
Re: Mastering PostgreSQL in Application Development
#39Looks interesting, wish I could "preview" before buying. Thankfully before venturing out on my own in the web development world, I was a member on a small business analytics team were we would all regularly write 3+ page SQL queries for reports. Sometimes they's take days to run. It was awesome and horrifying all at once but a good experience nonetheless and has allowed me to do what I do today.
Re: Mastering PostgreSQL in Application Development
#40Look interesting but I'm not crazy about the fact that to get the source + data, I have to get the $90 version.
Yep, the only version that's attractive enough (enterprise) is about 3/4 of the minimum wage here. I can't buy it, and it's a hard sell to my bosses, especially when the company doesn't even have more than 10 employees.