Dear MySQL users, MaxDB users and friends,
Several co-workers have spoken to me on the length of the MaxDB series postings. I fully agree that most postings are too long for a blog. But we do have a very eager plan to publish a complete online class. This is causing long postings and we can’t make them much shorter. We try to structure the articles in a similar way like a web page to make reading and navigating easier. Every posting has a table of contents, is devided into sections and has a fixed structure. For offline reading, printing and as a reference we will soon publish a PDF document with all postings of the series.
The experiment to use the medium of a blog for a class will continue as long as the readers do not complain. But we will add a “read more” link to the fixed structure of every posting. That means, we will present only the beginning of a posting on PlanetMySQL and you have to click on a “read more” link for the full text which might get you to a different URL. The link will be added shortly after the “In this issue” section of the posting which shows the table of contents. However, this posting is short enough so that it will not use a “read more” link.
In this issue
This issue is a follow-up on the last issue MaxDB series: User concept, authorization and schemata. We continue to explain the user concept of MaxDB. MaxDB distinguishes between “Administrators” – as we called them – and “SQL users”. The group of “Administrators” (Database Manager operators, DBM operators) and the “root” user (Database System Administrator, the SYSDBA) have been discussed in depth. The three different classes of “SQL users” (Databases users) have been introduced: DBA, STANDARD, RESOURCE. It has been shown how to grant privileges to an SQL user and what an SQL schema is. Detailed hands-on examples that show how to create users and how to use the SQL statements GRANT and REVOKE are left as an exercise to the reader.
You already learned everything you need to know about the user concept. What follows is only sugar.
