4 ms·
How do people keep track on all the features that are added in RDMS? When you know the basic stuff like SELECT / JOIN / indexes ect ... how do you stay relevent
by Thaxll 6y ago
How do people keep track on all the features that are added in RDMS? When you know the basic stuff like SELECT / JOIN / indexes ect ... how do you stay relevent with new things added?
- bhahn 6y agoNot a direct answer to your question, but there are two ways that I usually learn about new Postgres features. 1. Through blog posts like this 2. Needing something in the moment and googling. To elaborate on #2, I learned about partial indices when I was at a situation at work when I needed to optimize indices for a heavily used table. Google eventually brought me to their excellent docs and SO posts that mentioned them.
- VPenkov 6y agoI work for a fintech company and I'm not much of a SQL guy but I often hear how we've reached some limit of what PostgreSQL can do, and every update is a huge deal, even the patch versions. So I guess it's tech like any other. The more you know and use, the more you're aware of the recent developments. Like pretend you know enough javascript to build small promotional websites with some animations as you scroll down the page. You probably don't care, and are not aware, of the recent developments around optional chaining operators.
- jkatz05 6y agoThe PostgreSQL community tries to keep a list of new features that are added in its feature matrix: https://www.postgresql.org/about/featurematrix/ https://www.postgresql.org/about/featurematrix/ This is not an exhaustive list, but it contains a lot. You would still have to cull information from release notes: https://www.postgresql.org/docs/release/ https://www.postgresql.org/docs/release/ Or looking at the documentation page for a command (e.g. SELECT), or as per other suggestions, reading blogs/articles.
- castorp 6y ago> How do people keep track on all the features that are added in RDMS? By reading the release notes
- anarazel 6y agoYou don't necessarily need to. You might just transparently use them in a lot of cases. In others you'll just read the docs when you need to do something specific.
- baq 6y agoread the table of contents of the RDBMS you use. twice. do it again next day first thing. then read the chapters you didn't understand the title or haven't heard about the concept. this might take a while if you only know about select and join and create index - abstractions SQL provides are more leaky than rusty buckets and the manual is there to tell you everything about these and how to work with them. then it's 'just' a matter of keeping up with the delta by reading release notes.
- mixmastamyk 6y agohttps://postgresweekly.com/ https://postgresweekly.com/
- dpc_pw 6y agoNew features often come handy if you have a very specific need and usually you don't really need them at all and you can stick to common-SQL features. You often discover them when you search online looking for some blogs and stackoverflow threads, and then someone mentioned "you can get this done using XYZ in psql", and then you start reading what's that about.