dirkjonker
commented
6 years ago I tried splitting it up a bit and updating the abilities. It is however quite a large subject, it would be better to discuss this with a larger group in front of a whiteboard.
Good start. The whole 'RDBMS' repetition is a bit awkward; but maybe it's unavoidable. I guess the idea is that people can substitute their own RDBMS of choice? So that if one can do it with Postgres or MariaDB or with Oracle, it's okay?
I think the 'RDBMS SQL basics' is a bit too big; I think if you'd take out joins into a separate topic, it'll be halved in size.
The "RDBMS SQL advanced techniques" shows very much to the left, that's a bit awkward since based on it's complexity it should be more to the right. Maybe it should depend on 'RDBMS Indexes' and 'RDBMS Constraints'?
Of a more general note; I see myself going to 'abilities' all the time to figure out what the topic is about. I think most of the content should be moved from 'abilities' to the description of the topic, and the 'abilities' section should contain much more detailed abilities.
For example, the ability Set operations is not really an ability. If Set operations is moved to the description, an ability could be (for example) Use INTERSECT to find values that exist in two different query resultsets