-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #464 from codenotary/chore_upgrade_doc
chore: new sql statements
- Loading branch information
Showing
3 changed files
with
49 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
# User Management | ||
|
||
<WrappedSection> | ||
|
||
### CREATE USER | ||
|
||
Users can be created with the `CREATE USER` statement as follows: | ||
|
||
```sql | ||
CREATE USER user1 WITH PASSWORD 'user1Password!' READWRITE; | ||
``` | ||
|
||
Possible permissions are: `READ`, `READWRITE` and `ADMIN`. | ||
|
||
An admin user is able to fully manage the current database. | ||
|
||
</WrappedSection> | ||
|
||
<WrappedSection> | ||
|
||
### ALTER USER | ||
|
||
User password and permissions can be modified with the `ALTER USER` statement as follows: | ||
|
||
```sql | ||
ALTER USER user1 WITH PASSWORD 'newUser1Password!' ADMIN; | ||
``` | ||
|
||
</WrappedSection> | ||
|
||
<WrappedSection> | ||
|
||
### DROP USER | ||
|
||
An existing user can be deleted. | ||
Deletion is logically done and the user can be reactivated by executing an `ALTER USER` statement. | ||
|
||
```sql | ||
DROP USER user1; | ||
``` | ||
|
||
</WrappedSection> |