Chapter 45. GDBase Administration

Table of Contents

General information
GDBase setup
Database log-in
Default user
Administrator accounts
Creating an administartor account
Changing the administrator password
Users
Adding new users
User properties
Changing user properties
Displaying user properties
Table ownership
User Privileges
Changing user password
Deleting users
Access Control
Determining access privileges
Default Table Properies
Controlling queries
SHOW PROCESS
KILL PROCESS
PAUSE PROCESS
RESUME PROCESS
Commands available from user interface level
Additional information
Resetting user privileges

This chapter is devoted to various adminstartive task in GDBase: user accounts, user privileges, access control.

General information

GDBase setup

To use GDBase you first need to create an Alias. To do this go to the Services tab. If the tab is not visible select 'Window -> Services' from the main menu. To add a new alias select 'Add Alias' from the right click menu. A new window 'Add Alias' shows. You need to fill in the fields: 'Alias Name' , 'Database Drive' and 'Database URL' . In 'Database Drive' choose GDBase . In 'Database URL' write the host address (remote) or an existing catalog, which will be used to store the database files. Do not put any other files in this catalog.

When creating an alias to a new GDBase database leave the login and passwords empty. Do the same if you are connecting to a database as the default user. Otherwise provide your username and password.

You can also create an Alias by using a Gython function. The syntax is the following:

Syntax: To set alias with the default name:

dbAlias([driver_name, database_URL, user_name, user_password]) 
	

To set custom alias:

dbAlias([driver_name, database_URL, user_name, user_password], alias_name)   
	

To set custom alias as default:

dbAlias([driver_name, database_URL, user_name, user_password], alias_name, default = 1)       
    

Example 45.1. 

Linux syntax:

dbAlias(['gdbase.JDBC', 'jdbc:gdbase:/home/user/dbfolder','',''], 'myDB');
                

Windows syntax:

dbAlias(['gdbase.JDBC', 'jdbc:gdbase:C:/project/dbfolder', '',''], 'myDB'); 
                

It is possible to control whether remote database connections use SSL or not: select Tools | Options from the main menu, go to the Gornik | SSL tab and check or uncheck the Use SSL box, as required. In the case when you want to ovverride this setting and force a secure SSL connection with a particular database connection you can append the option ?useSSL=true to the database URL. If you wanto to force a non-SSL connection, append the ?useSSL=false option to the database URL.

Database log-in

GDBase requires the user to log in before starting work. This process requires the user to provide a unique combination of username and password. If the log-in fails, the system returns the authorization denied message. For security reasons the system does not inform the user which log-in fields had incorrect value.

Note

Username and password are case sensitive.

It is not possible to use GDBase without logging in. It is possible to log in as a default user. See the section Default user for more details.

Default user

Whenever a new GDBase database is launched, a default user is always created. This user has an empty login and empty password.