CUBRID Manual EN 8.4.1

cubrid_real_escape_string

2012-05-22T02:40:08-07:00

cubrid_real_escape_string

Description

The cubrid_real_escape_string function returns the escaped string version of the given string. Follow two escape sequence methods should be supported. On the quoted escape sequence, a string quoted with " or ' can be applied when system parameter ansi_quotes is set to "yes". If this option is set to "no", only a string quoted with ' can be applied. The default value is "no".

Quoted escape sequence:

A ' inside a string quoted with ' may be written as ' '
A " inside a string quoted with " may be written as "" (applied when ansi_quotes=yes)
A ' inside a string quoted with " needs no special treatment and need not be doubled or escaped. (applied when ansi_quotes=yes)
In the same way, " inside a string quoted with ' needs no special treatment.

Backslash escape sequence: This sequence is on by system parameter no_backslash_escapes.

The following characters can be escaped by backslash: \', \", \n, \r, \t, \\, \% \_.

If this option is set to "no", backslash escaping will work. The default value is "yes".

Syntax

string cubrid_real_escape_string (string $unescaped_string [, resource $link_identifier ] )

unescaped_string : The string that is to be escaped.
conn_identifier : The CUBRID connection. If the link identifier is not specified, the last link opened by cubrid_connect() is assumed.

Return Value

Success : Escaped characters
Failure : FALSE

Example

< ?php

$conn = cubrid_connect("localhost", 33000, "demodb");

$unescaped_str = ' !"#$%&\'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~';

$escaped_str = cubrid_real_escape_string($unescaped_str);

$len = strlen($unescaped_str);

@cubrid_execute($conn, "DROP TABLE cubrid_test");

cubrid_execute($conn, "CREATE TABLE cubrid_test (t char($len))");

cubrid_execute($conn, "INSERT INTO cubrid_test (t) VALUES('$escaped_str')");

$req = cubrid_execute($conn, "SELECT * FROM cubrid_test");

$row = cubrid_fetch_assoc($req);

var_dump($row);

cubrid_close_request($req);

cubrid_disconnect($conn);

The above example will output:

array(1) {

["t"]=>

string(95) " !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~"

}

CUBRID Characteristics

2012-04-19T03:36:30-07:00

CUBRID Characteristics

Transaction Support

CUBRID supports the following features to completely ensure the atomicity, consistency, isolation and durability in transactions.

Supporting commit, rollback, savepoint per transaction
Ensuring transaction consistency in the event of system or database failure
Ensuring transaction consistency between replications
Supporting multiple granularity locking of databases, tables and records
Resolving deadlocks automatically
Supporting distributed transactions (two-phase commit)

Database Backup and Restore

A database backup is the process of copying CUBRID database volumes, control files and log files; a database restore is the process of restoring the database to a certain point in time using backup files, active logs and archive logs copied by the backup process. For a restore, there must be the same operating system and the same version of CUBRID installed as in the backup environment.
The backup methods which CUBRID supports include online, offline and incremental backups; the restore methods include restore using incremental backups as well as partial and full restore.

Table Partitioning

Partitioning is a method by which a table is divided into multiple independent logical units. Each logical unit is called a partition, and each partition is divided into a different physical space. This will lead performance improvement by only allowing access to the partition when retrieving records. CUBRID provides three partitioning methods:

Range partitioning: Divides a table based on the range of a column value
Hash partitioning: Divides a table based on the hash value of a column
List partitioning: Divides a table based on the column value list

Supports a Variety of Index Functions

CUBRID supports the following index functions to utilize indices while executing a variety of conditional queries.

Descending Index Scan: Descending Index Scan is available only with Ascending Index Scan, without creating separate reverse indexes.
Covering Index: When the column of a SELECT list is included in the index, the requested data can be obtained with an index scan.
ORDER BY Clause Optimization: If the required record sorting order is identical to the order of indices, no additional sorting is required (Skip ORDER BY).
GROUP BY Clause Optimization: If all columns in the GROUP BY clause are included in the indices, they are available to use while executing queries. Therefore, no additional sorting is required (Skip GROUP BY).

HA

CUBRID provides High Availability (HA) to minimize system down time while continuing normal operation of server in the event of hardware, software, or network failure. The structure of CUBRID HA is shared-nothing. CUBRID monitors its system and status on a real time basis with the CUBRID Heartbeat and performs failover when failure occurs. It follows the two steps below to synchronize data from the master database server to slave database server.

A transaction log multiplication step where the transaction log created in the database server is replicated in real time to another node
A transaction log reflection step where data is applied to the slave database server through the analysis of the transaction log being replicated in real time

Java Stored Procedure

A stored procedure is a method to decrease the complexity of applications and to improve the reusability, security and performance through the separation of database logic and middleware logic. A stored procedure is written in Java (generic language), and provides Java stored procedures running on the Java Virtual Machine (JVM). To execute Java stored procedures in CUBRID, the following steps should be performed:

Install and configure the Java Virtual Machine
Create Java source files
Compile the files and load Java resources
Publish the loaded Java classes so they can be called from the database
Call the Java stored procedures

Click Counter

In the Web, it is a common scenario to count and keep the number of clicks to the database in order to record retrieval history.

The above scenario is generally implemented by using the SELECT and UPDATE statements; SELECT retrieves the data and UPDATE increases the number of clicks for the retrieved queries.

This approach can cause significant performance degradation due to increased lock contention for UPDATE when a number of SELECT statements are executed against the same data.

To address this issue, CUBRID introduces the new concept of the click counter that will support optimized features in the Web in terms of usability and performance, and provides the INCR function and the WITH INCREMENT FOR statement.

Extending the Relational Data Model

Collection

For the relational data model, it is not allowed that a single column has multiple values. In CUBRID, however, you can create a column with several values. For this purpose, collection data types are provided in CUBRID. The collection data type is mainly divided into SET, MULTISET and LIST; the types are distinguished by duplicated availability and order.

SET : A collection type that does not allow the duplication of elements. Elements are stored without duplication after being sorted regardless of their order of entry.
MULTISET : A collection type that allows the duplication of elements. The order of entry is not considered.
LIST : A collection type that allows the duplication of elements. Unlike with SET and MULTISET, the order of entry is maintained.

Inheritance

Inheritance is a concept to reuse columns and methods of a parent table in those of child tables. CUBRID supports reusability through inheritance. By using inheritance provided by CUBRID, you can create a parent table with some common columns and then create child tables inherited from the parent table with some unique columns added. In this way, you can create a database model which can minimize the number of columns.

Composition

In a relational database, the reference relationship between tables is defined as a foreign key. If the foreign key consists of multiple columns or the size of the key is significantly large, the performance of join operations between tables will be degraded. However, CUBRID allows the direct use of the physical address (OID) where the records of the referred table are located, so you can define the reference relationship between tables without using join operations.

That is, in an object-oriented database, you can create a composition relation where one record has a reference value to another by using the column displayed in the referred table as a domain (type), instead of referring to the primary key column from the referred table.

Introduction to CUBRID Manual

2012-04-19T03:36:29-07:00

Introduction to Manual

Manual Contents

The contents of the CUBRID Database Management System (CUBRID DBMS) product manual are as follows:

Introduction to CUBRID : This chapter provides a description of the structure and characteristics of the CUBRID DBMS.
Getting Started with CUBRID : The "Getting Started with CUBRID" provides users with a brief explanation on what to do when first starting CUBRID. The chapter contains information on new features added to CUBRID, on how to install and execute the system, and provides a simple guide on how to use the CSQL Interpreter and CUBRID Manager. The chapter also includes examples of how to write application programs using JDBC, PHP, ODBC, CCI, etc.
CSQL Interpreter : CSQL is an application that allows you to use SQL statements through a command-driven interface. This chapter explains how to use the CSQL Interpreter and associated commands.
CUBRID SQL Guide : This chapter describes SQL syntaxes such as data types, functions and operators, data retrieval or table manipulation. The chapter also provides SQL syntaxes used for indexes, triggers, partitioning, serial and user information changes, etc.
Administrator's Guide : This chapter provides instructions on how to create, drop, back up, restore and migrate a database, and executing CUBRID HA. Also it includes instructions on how to use CUBRID utilities, which starts and stops the Server, Broker and CUBRID Manager servers, etc.
Performance Tuning : The "Performance Tuning" chapter provides instructions on setting system parameters that may influence the performance. This chapter provides information on how to use the configuration file for the Server and Broker, and describes the meaning of each parameter.
API Reference : This chapter provides information on JDBC API, ODBC API, OLE DB API, PHP API, and CCI API.

Manual Conventions

The following table provides conventions on definitions used in the CUBRID Database Management System product manual to identify "statements," "commands" and "reference within texts."

Convention	Description	Example
Italics	Italics type is used to show the variable names.	persistent: stringVariableName
Boldface	Boldface type is used for names such as the member function name, class name, constants, CUBRID keyword or names such as other required characters.	fetch ( ) member function class odb_User
Constant Width	Constant Width type is used to show segments of code example or describes a command's execution and results.	csql database_name
UPPER-CASE	UPPER-CASE is used to show the CUBRID keyword (see Boldface).	SELECT
Single Quotes (' ')	Single quotes (' ') are used with braces and brackets, and shows the necessary sections of a syntax. Single quotes are also used to enclose strings.	{'{'const_list'}'}
Brackets ([ ])	Brackets ([ ]) indicate optional parameters or keywords.	[ONLY]
Underline( _ )	Underline (_) indicates a default keyword if no keyword is specified.	[DISTINCT\|UNIQUE\|ALL]
Vertical bar( \| )	Vertical bar (\|) indicates that one or another option can be specified.	[COLUMN\|ATTRIBUTE]
Braces around parameters({ })	Braces around parameters indicate that one of those parameters must be specified in a statement syntax.	{2, 4, 6}
Braces with ellipsis({ }...)	Braces before an ellipsis indicate that a parameter can be repeated.	{, class_name}...
Angle brackets(< >)	Angle brackets indicate a single key or a series of key strokes.	<Ctrl+n>

Savepoint and Partial Rollback

2012-04-19T03:36:55-07:00

Savepoint and Partial Rollback

Description

A savepoint is established during the transaction so that database changes made by the transaction are rolled back to the specified savepoint. Such operation is called a partial rollback. In a partial rollback, database operations (insert, update, delete, etc.) after the savepoint are rolled back, and transaction operations before it are not rolled back. The transaction can proceed with other operations after the partial rollback is executed. Or the transaction can be terminated with the COMMIT WORK or ROLLBACK WORK statement. Note that the savepoint does not commit the changes made by the transaction.

A savepoint can be created at a certain point of the transaction, and multiple savepoints can be used for a certain point. If a partial rollback is executed to a savepoint before the specified savepoint or the transaction is terminated with the COMMIT WORK or ROLLBACK WORK statement, the specified savepoint is removed. The partial rollback after the specified savepoint can be performed multiple times.

Savepoints are useful because intermediate steps can be created and named to control long and complicated utilities. For example, if you use a savepoint during the update operation, you don't need to perform all statements again when you made a mistake.

Note: In order for savepoints to work, autocommit option must be disabled.

Syntax 1

SAVEPOINT mark

mark:

_ a SQL identifier

_ a host variable (starting with :)

If you make mark all the same value when you specify multiple savepoints in a single transaction, only the latest savepoint appears in the partial rollback. The previous savepoints remain hidden until the rollback to the latest savepoint is performed and then appears when the latest savepoint disappears after being used.

Syntax 2

ROLLBACK [ WORK ] [ TO [ SAVEPOINT ] mark ] [ ]

mark:

_ a SQL identifier

_ a host variable (starting with :)

Previously, the ROLLBACK WORK statement canceled all database changes added since the latest transaction. The ROLLBACK WORK statement is also used for the partial rollback that rolls back the transaction changes after the specified savepoint.

If mark value is not given, the transaction terminates canceling all changes including all savepoints created in the transaction. If mark value is given, changes after the specified savepoint are canceled and the ones before it are remained.

Example

The following example shows how to roll back part of the transaction.

First, set savepoints SP1 and SP2.

CREATE TABLE athlete2 (name VARCHAR(40), gender CHAR(1), nation_code CHAR(3), event VARCHAR(30));

INSERT INTO athlete2(name, gender, nation_code, event)

VALUES ('Lim Kye-Sook', 'W', 'KOR', 'Hockey');

SAVEPOINT SP1;

SELECT * from athlete2;

INSERT INTO athlete2(name, gender, nation_code, event)

VALUES ('Lim Jin-Suk', 'M', 'KOR', 'Handball');

SELECT * FROM athlete2;

SAVEPOINT SP2;

RENAME TABLE athlete2 AS sportsman;

SELECT * FROM sportsman;

ROLLBACK WORK TO SP2;

In the example above, the name change of the athlete2 table is rolled back by the partial rollback. The following example shows how to execute the query with the original name and examining the result.

SELECT * FROM athlete2;

DELETE FROM athlete2 WHERE name = 'Lim Jin-Suk';

SELECT * FROM athlete2;

ROLLBACK WORK TO SP2;

In the example above, deleting 'Lim Jin-Suk' is discarded by rollback work to SP2 command.

The following example shows how to roll back to SP1.

SELECT * FROM athlete2;

ROLLBACK WORK TO SP1;

SELECT * FROM athlete2;

COMMIT WORK;

DROP INDEX Clause

2012-04-19T03:36:37-07:00

DROP INDEX Clause

Description

You can delete an index defined for a column by using the DROP INDEX clause.

Syntax

ALTER [ TABLE | CLASS ] table_name DROP [ REVERSE ] [ UNIQUE ] INDEX index_name

REVERSE : Specifies that the index to be dropped is a reverse index.
UNIQUE : Specifies that the index to be dropped is a unique index.
table_name : Specifies the name of a table that has an index attribute to be deleted.
index_name : Specifies the name of an index to be deleted.

Examples

ALTER TABLE a_tbl DROP INDEX i_a_tbl_age;

ALTER TABLE a_tbl DROP UNIQUE INDEX i_a_tbl_age;

Installing the PHP Module

2012-04-19T03:36:31-07:00

Installing the PHP Module

Installing Required Software

You should install the software below, first:

Apache Web server : Version 2.0 or later
PHP : Version 5.2 or later
CUBRID

Downloading PHP Modules

Download drives from ftp://ftp.cubrid.org/CUBRID_Drivers/PHP_Driver/. For latest information on PHP drives, visit Web site (http://www.cubrid.org/php_api_for_cubrid).

Installing for Windows

Store the php_cubrid.dll file under PHP extension directory (default location : C:\Program Files\PHP\ext).
Configure the system configuration variable. The environment variable value of PHPRC should be C:\Program Files\PHP and %PHPRC% and %PHPRC%ext" should be added to the value of Path environment variable.
Add the following line at the end of the php.ini file (default location : C:\Program Files\PHP\php.ini).
- [PHP_CUBRID] extension=php_cubrid.dll
Once configuration is complete, restart the Web server.

Installing for Linux

Store the cubrid.so file under PHP extensions directory. The file is usually located under /usr/lib/php5/20090626 in PHP 5.3.3; however, the location depends on PHP versions).
Add the following line at the end of the php.ini file (default location : /etc/php5/apache2/php.ini).
- [CUBRID] extension=cubrid.so
Once configuration is complete, restart the Web server.

Installing Package

Using the Installation Wizard for Windows

You can download CUBRID PHP API Installer from http://www.cubrid.org/php_install_wizard.

Installing by Using PEAR Package for Ubuntu Linux

First, you must set up phpize and PEAR package. Follow the steps below.

Install Apache Web server and PHP. For information on installation of Apache Web server and PHP, visit the Web site (http://www.cubrid.org/cubrid_apache_php_ubuntu).
Execute the following line to set up phpize.
1. sudo apt-get install php5-dev
Execute the following line to install PEAR package.
1. sudo apt-get install php-pear
Execute the pecl command in PEAR package so that the latest CUBRID PHP extension can be installed.
- sudo pecl install cubrid
- To install the earlier version of PHP drivers, you must specify the desired version.
1. sudo pecl install cubrid-8.3.0.0005
Add the following line at the end of the php.ini file (default location : /etc/php5/apache2/php.ini).
1. [CUBRID] extension=cubrid.so
Once configuration is complete, restart the Web server.

Installing by Using PEAR Package for Linux Except for Version Ubuntu

First, you must install phpize and PEAR package. Follow the steps below.

Set up phpzie. The version php-dev must be PHP 5.2.x or PHP 5.3.x. If you are using the earlier version of PHP, update PHP before proceeding with installation.
1. yum install php-devel
Download PEAR package.
1. wget http://pear.php.net/go-pear.phar
Install PEAR package.
1. php go-pear.phar
Install the latest verions of CUBRID-PHP Extension.
1. pecl install cubrid
- To install the earlier version of PHP drivers, you must specify the desired version.
- sudo pecl install cubrid-8.3.0.0005
Add the following line at the end of the php.ini file (default location : /etc/php5/apache2/php.ini).
1. [CUBRID] extension=cubrid.so
Once configuration is complete, restart the Web server.
Note If you use the phpinfo() function to create test.php and verify that CUBRID configuration page is properly displayed after entering http://<IP address in which Web server is installed>/test.php, it means installation is successfully done.

Setting up the JDBC Environment

2012-04-19T03:36:31-07:00

Setting up the JDBC Environment

System Requirements

JDK 1.6 or later
CUBRID 2008 R1.0 or later
CUBRID JDBC Driver 2008 R1.0 or later

Installing and Configuring Java Environment

You must already have Java installed and the JAVA_HOME environment variable set on your system. To install Java, download it from the Java homepage (http://java.sun.com). For more information, see Environment Settings for Java Stored Functions/Procedures.

Configuring Envrionment Variables for Windows

After installing JAVA, double click [My Computer] and click [System Properties]. In the [Advanced] tab, click [Envrionment Variables]. The [Environment Variables] dialog will appear.

In the [System Variables], click [New]. Enter JAVA_HOME and Java installation path such as C:\Program Files\Java\jdk1.6.0_16 and then press [Enter].

Select "Path" and then click [Edit]. Add %JAVA_HOME%bin to the variable and then click [OK].

You can configure JAVA_HOME and PATH in the shell.

set JAVA_HOME= C:\Program Files\Java\jdk1.6.0_16

set PATH=%PATH%;%JAVA_HOME%bin

Configuring the Environment Variables for Linux

Specify the directory path where Java is installed (example : /usr/java/jdk1.6.0_16) in the JAVA_HOME environment variable, and add $JAVA_HOME/bin to the PATH environment variable.

export JAVA_HOME=/usr/java/jdk1.6.0_16 //bash

export PATH=$JAVA_HOME/bin:$PATH //bash

setenv JAVA_HOME /usr/java/jdk1.6.0_16 //csh

set path = ($JAVA_HOME/bin $path) //csh

JDBC Driver Setting

To use the JDBC, set your CLASSPATH environment variable to the path where the CUBRID JDBC driver is located.

The CUBRID JDBC driver (cubrid_jdbc.jar) is located in jdbc directory which is subdirectory where CUBRID is installed.

Configuring the CLASSPATH Environment Variables for Windows

set CLASSPATH=%CUBRID%jdbccubrid_jdbc.jar:.

Configuring the CLASSPATH Environment Variables for Linux

export CLASSPATH=$HOME/CUBRID/jdbc/cubrid_jdbc.jar:.

Note If a CUBRID JDBC driver has been installed in the same library directory ($JAVA_HOME/jre/lib/ext) where the JRE is located, it may be loaded ahead of the server-side JDBC driver used by the Java stored procedure, causing it to malfunction. In a Java stored procedure environment, make sure not to install the generic CUBRID JDBC driver in the directory where the JRE is installed ($JAVA_HOME/jre/lib/ext).

Installing and Running on Linux

2012-04-19T03:36:31-07:00

Installing and Running on Linux

Details to Check when Installing

Check the following before installing CUBRID for Linux.

Category	Description
Operating system	Only supports glibc 2.3.4 or later. The glibc version can be checked as follows: rpm -q glibc
64-bit	Since version 2008 R2.0, CUBRID supports both 32-bit and 64-bit Linux. You can check the version as follows: % uname -a Linux host_name 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 x86_64 x86_64 x86_64 GNU/Linux Make sure to install the CUBRID 32-bit version on 32-bit Linux and the CUBRID 64-bit version on 64-bit Linux. The followings are the libraries that should be added. Curses Library (rpm -q ncurses) gcrypt Library (rpm -q libgcrypt stdc++ Library (rpm -q libstdc++)
Available free memory space	1 GB or more recommended.
Available free disk space	2 GB or more recommended (500 MB is required for initial installation and 1.5 GB is required for creating the default option database).
Required software	The CUBRID Manager and Java stored procedures require the Java Runtime Environment (JRE) version 1.6 or later.

Installing CUBRID

The installation program consists shell scripts that contain binary; thus it can be installed automatically. The following example shows how to install CUBRID with the "CUBRID-8.3.0.0312-linux.x86_64.sh" file on the Linux.

[cub_user@cubrid ~]$ sh CUBRID-8.3.1.0168-linux.x86_64.sh

Do you agree to the above license terms? (yes or no) : yes

Do you want to install this software(CUBRID) to the default(/home1/cub_user/CUBRID) directory? (yes or no) [Default: yes] : yes

Install CUBRID to '/home1/cub_user/CUBRID' ...

In case a different version of the CUBRID product is being used in other machines, please note that the CUBRID 2008 R3.1 servers are only compatible with the CUBRID 2008 R3.1 clients and vice versa.

Do you want to continue? (yes or no) [Default: yes] : yes

Copying old .cubrid.sh to .cubrid.sh.bak ...

CUBRID has been successfully installed.

demodb has been successfully created.

If you want to use CUBRID, run the following commands

% . /home1/cub_user/.cubrid.sh

% cubrid service start

As shown in the example above, after installing the downloaded file (CUBRID-8.3.1.0168-linux.x86_64.sh), the CUBRID related environment variables must be set in order to use the CUBRID database. Such setting has been made automatically when logging in the concerned terminal. Therefore there is no need to re-set after the first installation.

[cub_user@cubrid ~]$ . /home1/cub_user/.cubrid.sh

After the CUBRID Manager is installed, you can start the CUBRID Manager server and Broker as follows:

[cub_user@cubrid ~]$ cubrid service start

After starting the CUBRID service, if you wish to check whether the service was properly started, then check whether the cub_* processes have been started with grep (as shown below).

[cub_user@cubrid ~]$ ps -ef | grep cub_

cub_user 15200 1 0 18:57 ? 00:00:00 cub_master

cub_user 15205 1 0 18:57 pts/17 00:00:00 cub_broker

cub_user 15210 1 0 18:57 pts/17 00:00:00 query_editor_cub_cas_1

cub_user 15211 1 0 18:57 pts/17 00:00:00 query_editor_cub_cas_2

cub_user 15212 1 0 18:57 pts/17 00:00:00 query_editor_cub_cas_3

cub_user 15213 1 0 18:57 pts/17 00:00:00 query_editor_cub_cas_4

cub_user 15214 1 0 18:57 pts/17 00:00:00 query_editor_cub_cas_5

cub_user 15217 1 0 18:57 pts/17 00:00:00 cub_broker

cub_user 15222 1 0 18:57 pts/17 00:00:00 broker1_cub_cas_1

cub_user 15223 1 0 18:57 pts/17 00:00:00 broker1_cub_cas_2

cub_user 15224 1 0 18:57 pts/17 00:00:00 broker1_cub_cas_3

cub_user 15225 1 0 18:57 pts/17 00:00:00 broker1_cub_cas_4

cub_user 15226 1 0 18:57 pts/17 00:00:00 broker1_cub_cas_5

cub_user 15229 1 0 18:57 ? 00:00:00 cub_auto start

cub_user 15232 1 0 18:57 ? 00:00:00 cub_js start

Installing CUBRID (rpm File)

You can install CUBRID by using rpm file that is created on CentOS5. The way of installing and uninstalling CUBRID is the same as that of using general rpm utility. While CUBRID is being installed, a new system group (cubrid) and a user account (cubrid) are created. After installation is complete, you should log in with a cubrid user account to start a CUBRID service.

$ rpm -Uvh CUBRID-8.3.1.0168-el5.x86_64.rpm

When rmp is executed, CUBRID is installed in the cubrid home directory (/opt/cubrid) and related configuration file (cubrid.[c]sh) is installed in the /etc/profile.d directory. Note that demodb is not automatically installed. Therefore, you must executed /opt/cubrid/demo/make_cubrid_demo.sh. When installation is complete, enter the code below to start CUBRID.

[cubrid@cubrid ~]$ cubrid service start

Note You must check RPM dependency when installing with RPM. If you ignore (--nodeps) dependency, it may not be executed.
Even if you remove RPM, user accounts and databases that are created after installing, you must remove it manually, if needed.

Installing CUBRID on Fedora/CentoOS

To install CUBRID using the yum command, you should know where the CUBRID package is located. Choose appropriate location based on your operating system.

http://www.cubrid.org/yum_repository

For example, if you are using Fedora 16, execute the command below. In the example, fc16 refers to Fedora 16.

$ rpm -i http://yumrepository.cubrid.org/cubrid_repo_settings/8.4.0/cubridrepo-8.4.0-1.fc16.noarch.rpm

If you are using CentOS 6.2, execute the command below. In this example, el6.2 refers to CentOS.

$ rpm -i http://yumrepository.cubrid.org/cubrid_repo_settings/8.4.0/cubridrepo-8.4.0-1.el6.2.noarch.rpm

You can install the CUBRID package you have desired based on the command you execute. To install the latest version, execute the command below.

$ yum install cubrid

To install the earlier version, you should include version information in the command.

$ yum install cubrid-8.3.1

After installation is complete, configure environment variables including installation path of CUBRID and then apply them to system.

Installing CUBRID on Ubuntu

To install CUBRID using the apt-get command on Ubuntu, add the CUBRID storage first and then update the apt index.

$ sudo add-apt-repository ppa:cubrid/cubrid

$ sudo apt-get update

To install the latest version, execute the command below.

$ sudo apt-get install cubrid

To install the earlier version, you should include version information in the command.

$ sudo apt-get install cubrid-8.3.1

After installation is complete, configure environment variables including installation path of CUBRID and then apply them to system.

Upgrading CUBRID

When you specify an installation directory where the previous version of CUBRID is already installed, a message which asks to overwrite files in the directory will appear. Entering no will stop the installation.

Directory '/home1/cub_user/CUBRID' exist!

If a CUBRID service is running on this directory, it may be terminated abnormally.

And if you don't have right access permission on this directory(subdirectories or files), install operation will be failed.

Overwrite anyway? (yes or no) [Default: no] : yes

Choose whether to overwrite the existing configuration files during the CUBRID installation. Entering yes will overwrite and back up them as extension .bak files.

The configuration file (.conf or .pass) already exists. Do you want to overwrite it? (yes or no) : yes

Configuring Environment

You can modify the environment such as service ports etc. edit the parameters of a configuration file located in the $CUBRID/conf directory. See Environment Configuration for more information.

Installing CUBRID Interfaces

You can see the latest information on interface modules such as JDBC, PHP, ODBC, and OLE DB and install them by downloading files from http://www.cubrid.org/wiki_apis.

Installing CUBRID Tools

You can see the latest information on tools such as CUBRID Manager and CUBRID Query Browser and install them by downloading files from http://www.cubrid.org/wiki_tools.

RLIKE Conditional Expression

2012-04-19T03:36:52-07:00

REGEXP/RLIKE Conditional Expression

Description

The REGEXP and RLIKE conditional expressions are used interchangeably; A regular expressions is a powerful way to specify a pattern for a complex search. CUBRID uses Henry Spencer's implementation of regular expressions, which conforms the POSIX 1003.2 standards. The details on regular expressions are not described in this page. For more information on regular expressions, see Henry Spencer's regex(7).

The following list describes basic characteristics of regular expressions.

"." matches any single character(including new-line and carriage-return).
"[...]" matches one of characters within square brackets. For example, "[abc]" matches "a", "b", or "c". To represent a range of characters, use a dash (-). "[a-z]" matches any alphabet letter whereas "[0-9]" matches any single number.
"*" matches 0 or more instances of the thing proceeding it. For example, "xabc*" matches "xab", "xabc", "xabcc", and "xabcxabc" etc. "[0-9][0-9]*" matches any numbers, and ".*" matches every string.
To match special characters such as " ", " ", " ", and "", some must be escaped with the backslash () by specifying the value of no_backslash_escapes (default: yes) to no. For details on no_backslash_escapes, see Escape Special Characters.

The difference between REGEXP and LIKE are as follows:

The LIKE operator succeeds only if the pattern matches the entire value.
The REGEXP operator succeeds if the pattern matches anywhere in the value. To match the entire value, you should use "^" at the beginning and "$" at the end.
The LIKE operator is case sensitive, but patterns of regular expressions in REGEXP is not case sensitive. To enable case sensitive, you should use REGEXP BINARY statement.

In the syntax below, if expr matches pat, 1 is returned; otherwise, 0 is returned. If either expr or pat is NULL, NULL is returned.

The second syntax has the same meaning as the third syntax, which both syntaxes are using NOT.

Syntax

expr REGEXP|RLIKE [BINARY] pat

expr NOT REGEXP|RLIKE pat

NOT (expr REGEXP|RLIKE pat)

expr : Column or input expression
pat : Pattern used in regular expressions; not case sensitive

Example

-- When REGEXP is used in SELECT list, enclosing this with parentheses is required. But used in WHERE clause, no need parentheses.

-- case insensitive, except when used with BINARY.

SELECT name FROM athlete where name REGEXP '^[a-d]';

name

======================

'Dziouba Irina'

'Dzieciol Iwona'

'Dzamalutdinov Kamil'

'Crucq Maurits'

'Crosta Daniele'

'Bukovec Brigita'

'Bukic Perica'

'Abdullayev Namik'

-- : match a special character, when no_backslash_escapes=no

SELECT ('new line' REGEXP 'new

line');

('new

line' regexp 'new

line')

=====================================

-- ^ : match the beginning of a string

SELECT ('cubrid dbms' REGEXP '^cub');

('cubrid dbms' regexp '^cub')

===============================

-- $ : match the end of a string

SELECT ('this is cubrid dbms' REGEXP 'dbms$');

('this is cubrid dbms' regexp 'dbms$')

========================================

--.: match any character

SELECT ('cubrid dbms' REGEXP '^c.*$');

('cubrid dbms' regexp '^c.*$')

================================

-- a+ : match any sequence of one or more a characters. case insensitive.

SELECT ('Aaaapricot' REGEXP '^A+pricot');

('Aaaapricot' regexp '^A+pricot')

================================

-- a? : match either zero or one a character.

SELECT ('Apricot' REGEXP '^Aa?pricot');

('Apricot' regexp '^Aa?pricot')

==========================

SELECT ('Aapricot' REGEXP '^Aa?pricot');

('Aapricot' regexp '^Aa?pricot')

===========================

SELECT ('Aaapricot' REGEXP '^Aa?pricot');

('Aaapricot' regexp '^Aa?pricot')

============================

-- (cub)* : match zero or more instances of the sequence abc.

SELECT ('cubcub' REGEXP '^(cub)*$');

('cubcub' regexp '^(cub)*$')

==========================

-- [a-dX], [^a-dX] : matches any character that is (or is not, if ^ is used) either a, b, c, d or X.

SELECT ('aXbc' REGEXP '^[a-dXYZ]+');

('aXbc' regexp '^[a-dXYZ]+')

==============================

SELECT ('strike' REGEXP '^[^a-dXYZ]+$');

('strike' regexp '^[^a-dXYZ]+$')

================================

Remark

The following shows RegEx-Specer's license, which is library used to implement the REGEXP conditional expression.

This software is not subject to any license of the American Telephone

and Telegraph Company or of the Regents of the University of California.

Permission is granted to anyone to use this software for any purpose on

any computer system, and to alter it and redistribute it, subject

to the following restrictions:

1. The author is not responsible for the consequences of use of this

software, no matter how awful, even if they arise from flaws in it.

2. The origin of this software must not be misrepresented, either by

explicit claim or by omission. Since few users ever read sources,

credits must appear in the documentation.

3. Altered versions must be plainly marked as such, and must not be

misrepresented as being the original software. Since few users

ever read sources, credits must appear in the documentation.

4. This notice may not be removed or altered.

REGEXP Conditional Expression

2012-04-19T03:36:52-07:00

REGEXP/RLIKE Conditional Expression

Description

The following list describes basic characteristics of regular expressions.

"." matches any single character(including new-line and carriage-return).
"[...]" matches one of characters within square brackets. For example, "[abc]" matches "a", "b", or "c". To represent a range of characters, use a dash (-). "[a-z]" matches any alphabet letter whereas "[0-9]" matches any single number.
"*" matches 0 or more instances of the thing proceeding it. For example, "xabc*" matches "xab", "xabc", "xabcc", and "xabcxabc" etc. "[0-9][0-9]*" matches any numbers, and ".*" matches every string.
To match special characters such as " ", " ", " ", and "", some must be escaped with the backslash () by specifying the value of no_backslash_escapes (default: yes) to no. For details on no_backslash_escapes, see Escape Special Characters.

The difference between REGEXP and LIKE are as follows:

The LIKE operator succeeds only if the pattern matches the entire value.
The REGEXP operator succeeds if the pattern matches anywhere in the value. To match the entire value, you should use "^" at the beginning and "$" at the end.
The LIKE operator is case sensitive, but patterns of regular expressions in REGEXP is not case sensitive. To enable case sensitive, you should use REGEXP BINARY statement.

In the syntax below, if expr matches pat, 1 is returned; otherwise, 0 is returned. If either expr or pat is NULL, NULL is returned.

The second syntax has the same meaning as the third syntax, which both syntaxes are using NOT.

Syntax

expr REGEXP|RLIKE [BINARY] pat

expr NOT REGEXP|RLIKE pat

NOT (expr REGEXP|RLIKE pat)

expr : Column or input expression
pat : Pattern used in regular expressions; not case sensitive

Example

-- When REGEXP is used in SELECT list, enclosing this with parentheses is required. But used in WHERE clause, no need parentheses.

-- case insensitive, except when used with BINARY.

SELECT name FROM athlete where name REGEXP '^[a-d]';

name

======================

'Dziouba Irina'

'Dzieciol Iwona'

'Dzamalutdinov Kamil'

'Crucq Maurits'

'Crosta Daniele'

'Bukovec Brigita'

'Bukic Perica'

'Abdullayev Namik'

-- : match a special character, when no_backslash_escapes=no

SELECT ('new line' REGEXP 'new

line');

('new

line' regexp 'new

line')

=====================================

-- ^ : match the beginning of a string

SELECT ('cubrid dbms' REGEXP '^cub');

('cubrid dbms' regexp '^cub')

===============================

-- $ : match the end of a string

SELECT ('this is cubrid dbms' REGEXP 'dbms$');

('this is cubrid dbms' regexp 'dbms$')

========================================

--.: match any character

SELECT ('cubrid dbms' REGEXP '^c.*$');

('cubrid dbms' regexp '^c.*$')

================================

-- a+ : match any sequence of one or more a characters. case insensitive.

SELECT ('Aaaapricot' REGEXP '^A+pricot');

('Aaaapricot' regexp '^A+pricot')

================================

-- a? : match either zero or one a character.

SELECT ('Apricot' REGEXP '^Aa?pricot');

('Apricot' regexp '^Aa?pricot')

==========================

SELECT ('Aapricot' REGEXP '^Aa?pricot');

('Aapricot' regexp '^Aa?pricot')

===========================

SELECT ('Aaapricot' REGEXP '^Aa?pricot');

('Aaapricot' regexp '^Aa?pricot')

============================

-- (cub)* : match zero or more instances of the sequence abc.

SELECT ('cubcub' REGEXP '^(cub)*$');

('cubcub' regexp '^(cub)*$')

==========================

-- [a-dX], [^a-dX] : matches any character that is (or is not, if ^ is used) either a, b, c, d or X.

SELECT ('aXbc' REGEXP '^[a-dXYZ]+');

('aXbc' regexp '^[a-dXYZ]+')

==============================

SELECT ('strike' REGEXP '^[^a-dXYZ]+$');

('strike' regexp '^[^a-dXYZ]+$')

================================

Remark

The following shows RegEx-Specer's license, which is library used to implement the REGEXP conditional expression.

This software is not subject to any license of the American Telephone

and Telegraph Company or of the Regents of the University of California.

Permission is granted to anyone to use this software for any purpose on

any computer system, and to alter it and redistribute it, subject

to the following restrictions:

1. The author is not responsible for the consequences of use of this

software, no matter how awful, even if they arise from flaws in it.

2. The origin of this software must not be misrepresented, either by

explicit claim or by omission. Since few users ever read sources,

credits must appear in the documentation.

3. Altered versions must be plainly marked as such, and must not be

misrepresented as being the original software. Since few users

ever read sources, credits must appear in the documentation.

4. This notice may not be removed or altered.

Statement|Type-Related Parameters

2012-04-19T03:37:12-07:00

Statement/Type-Related Parameters

The following are parameters related to SQL statements and data types supported by CUBRID. The type and value range for each parameter are as follows:

Parameter Name	Type	Default Value
add_column_update_hard_default	bool	no
alter_table_change_type_strict	bool	no
ansi_quotes	bool	yes
block_ddl_statement	bool	no
block_nowhere_statement	bool	no
compat_numeric_division_scale	bool	no
default_week_format	int	0
group_concat_max_len	int	1024
intl_mbs_support	bool	no
no_backslash_escapes	bool	yes
only_full_group_by	bool	no
oracle_style_empty_string	bool	no
pipes_as_concat	bool	yes
plus_as_concat	bool	yes
require_like_escape_character	bool	no
return_null_on_function_errors	bool	no

add_column_update_hard_default

The add_column_update_hard_default parameter is used to determine whether or not to provide the hard_default value as the input value for a column when you add a new column to the ALTER TABLE … ADD COLUMN clause.

If a value for this parameter is set to yes, enter a new input value of a column as a hard default value when you have NOT NULL constraints but no DEFAULT constraints. If the parameter value is set to no, enter NULL, even if NOT NULL constraints exist. If a value for this parameter is set to yes and there is no hard default value for the column type to add, an error message will be displayed and a roll-back occurs. For the hard default for each type, see the CHANGE Clause of the ALTER TABLE statement.

-- add_column_update_hard_default=no

CREATE TABLE tbl (i INT);

INSERT INTO tbl VALUES (1),(2);

ALTER TABLE tbl ADD COLUMN j INT NOT NULL;

SELECT * FROM TBL;

i j

========================

2 NULL

1 NULL

-- add_column_update_hard_default=yes

CREATE TABLE tbl (i int);

INSERT INTO tbl VALUES (1),(2);

ALTER TABLE tbl ADD COLUMN j INT NOT NULL;

SELECT * FROM tbl;

i j

=========================

2 0

1 0

alter_table_change_type_strict

The alter_table_change_type_strict parameter is used to determine whether or not to allow the conversion of column values according to the type change, and the default value is no. If a value for this parameter is set to no, the value may be changed when you change the column types or when you add NOT NULL constraints; if it is set to yes, the value is not changed. For details, see CHANGE Clause in the CHANGE/MODIFY Clause.

ansi_quotes

ansi_quotes is a parameter that enclose symbols and character string to handle identifiers. The default value is yes. If this parameter value is set to yes, double quotations are handled as identifier symbols and single quotations are handled as character string symbols. If it is set to no, both double and single quotations are handled as character string symbols.

block_ddl_statement

block_ddl_statement is a parameter that restricts the execution of DDL (Data Definition Language) statements by the client. If the parameter is configured to no, the given client is allowed to execute DDL statements. If it is configured to yes, the client is not permitted to execute DDL statements. The default value is no.

block_nowhere_statement

block_nowhere_statement is a parameter that restricts the execution of UPDATE/DELETE statements without a condition clause (WHERE) by the client. If the parameter is configured to no, the given client is allowed to execute UPDATE/DELETE statements without a condition clause. If it is configured to yes, the client is not permitted to execute UPDATE/DELETE statements without a condition clause. The default value is no.

compact_numeric_division_scale

compat_numeric_division_scale is a parameter that configures the scale to be displayed in the result (quotient) of a division operation. If the parameter is configured to no, the scale of the quotient is 9 if it is configured to yes, the scale is determined by that of the operand. The default value is no.

default_week_format

The default_week_format parameter is used to set the default value for the mode attribute of the WEEK function. The default value is 0. For details, see WEEK Function.

group_concat_max_len

The group_concat_max_len parameter is used to limit the return value size of the GROUP_CONCAT function. The default value is 1024 bytes, the minimum value is 4 bytes, and the maximum value is 33,554,432 bytes. If the return value of the GROUP_CONCAT function exceeds the limitation, NULL will be returned.

intl_mbs_support

intl_mbs_support is a parameter that specifies whether or not to support multi-byte character set. If the parameter is configured to no, a multi-byte character set is not allowed if it is configured to yes, a multi-byte character set is allowed. To improve performance, it is recommended to configure the intl_mbs_support parameter to no and use alphabets for table and column names because operation cost for supporting multi-byte character set is high.

no_backslash_escapes

The no_backslash_escapes is used to determine whether or not to use backslash () as an escape character, and the default value is yes. If a value for this parameter is set to no, backslash () will be used as an escape character; if it is set to yes, backslash () will be used as a normal character. For details, see Escape Special Characters.

only_full_group_by

only_full_group_by is a parameter that specifies whether extended syntax about using GROUP BY statement is used or not.

If this parameter value is set to no, an extended syntax is applied thus, a column that is not specified in the GROUP BY statement can be specified in the SELECT column list. If it is set to yes, a column that is only specified in the GROUP BY statement can be the SELECT column list.

The default value is no. Therefore, specify the only_full_group_by parameter value to yes to execute queries by SQL standards. Because the extended syntax is not applied in this case, an error below is displayed.

ERROR: Attributes exposed in aggregate queries must also appear in the group by clause.

oracle_style_empty_string

oracle_style_empty_string is a parameter that improves compatibility with other DBMS (Database Management Systems) and specifies whether or not to process empty strings as NULL as in Oracle DBMS. If the oracle_style_empty_string parameter is configured to no, the character string is processed as a valid string if it is configured to yes, the empty string is processed as NULL.

pipes_as_concat

pipes_as_concat is a parameter about using a double pipe symbol. The default value is yes. If this parameter value is set to yes, a double pipe symbol is handled as a concatenation operator if no, it is handled as the OR operator.

plus_as_concat

The plus_as_concat parameter is a parameter for the use of the + operator, and the default value is yes. If a value for this parameter is set to yes, the + operator will be interpreted as a concatenation operator; if it is set to no, the operator will be interpreted as a numeric operator.

-- plus_as_concat = yes

SELECT '1'+'1';

'1'+'1'

======================

'11' SELECT '1'+'a';

'1'+'a'

======================

'1a'

-- plus_as_concat = no

SELECT '1'+'1';

'1'+'1'

==========================

2.000000000000000e+000

SELECT '1'+'a';

ERROR: Cannot coerce 'a' to type double.

require_like_escape_characterintl_mbs_support

The require_like_escape_character parameter is used to determine whether or not to use an ESCAPE character in the LIKE clause, and the default value is no. If a value for this parameter is set to yes and a value for no_backslash_escapes is set to no, backslash () will be used as an ESCAPE character in the strings of the LIKE clause, otherwise you should specify an ESCAPE character by using the LIKE… ESCAPE clause. For details, see LIKE Predicate.

return_null_on_function_errors

The return_null_on_function_errors parameter is used to define actions when errors occur in some SQL functions, and the default value is no. If a value for this parameter is set to yes, NULL is returned; if it is set to no, an error is returned when the error occurs in functions, and the related message is displayed.

The following SQL functions are affected by this system parameter.

ADDTIME
DATEDIFF
DAY
DAYOFMONTH
DAYOFWEEK
DAYOFYEAR
FROM_DAYS
FROM_UNIXTIME
HOUR
LAST_DAY
MAKEDATE
MAKETIME
MINUTE
MONTH
QUARTER
SEC_TO_TIME
SECOND
TIME
TIME_TO_SEC
TIMEDIFF
TO_DAYS
WEEK
WEEKDAY
YEAR

-- return_null_on_function_errors=no

SELECT HOUR('2010-01-01');

ERROR: Conversion error in time format.

-- return_null_on_function_errors=yes

SELECT HOUR('2010-01-01');

hour('2010-01-01')

======================

NULL

PHP API

2012-04-19T03:37:16-07:00

PHP API

Escape Special Characters

2012-05-22T02:27:45-07:00

Escape Special Characters

Description

CUBRID supports two kinds of methods to escape special characters. One is using quotes and the other is using backslash (\).

Escape with Quotes

If you set no for the system parameter ansi_quotes in the cubrid.conf file, you can use both double quotes (") and singe quotes (') to wrap strings. The default value for the ansi_quotes parameter is yes, and you can use only single quotes to wrap the string. The numbers 2 and 3 below are applied only if you set for the ansi_quotes parameter to no.

You should use two single quotes ('') for the single quotes included in the strings wrapped in single quotes.
You should use two double quotes ("") for the double quotes included in the strings wrapped in double quotes.
You don't need to escape the single quotes included in the string wrapped in double quotes.
You don't need to escape the double quotes included in the string wrapped in single quotes.

Escape with Backslash

You can use escape using backslash (\) only if you set no for the system parameter no_backslash_escapes in the cubrid.conf file. The default value for the no_backslash_escapes parameter is yes. Depending on the input value, the following are the special characters.

\' : Single quotes (')
\" : Double quotes (")
\n : Newline, linefeed character
\r : Carriage return character
\t : Tab character
\\ : Backslash
\% : Percent sign (%). For details, see the following description.
\_ : Underbar (_). For details, see the following description.

For all other escapes, the backslash will be ignored. For example, "\x" is the same as entering only "x".

\% and \_ are used in the pattern matching syntax such as LIKE to search percent signs and underbars and are used as a wildcard character if there is no backslash. Outside of the pattern matching syntax, "\%"and "\_" are recognized as normal strings not wildcard characters. For details, see LIKE Predicate.

Example 1

The following is the result of executing Escape if a value for the system parameter ansi_quotes in the cubrid.conf file is no, and a value for no_backslash_escapes is no.

SELECT STRCMP('single quotes test('')', 'single quotes test(\')');

strcmp('single quotes test('')', 'single quotes test('')')

=============================================================

SELECT STRCMP("\a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z", "a\bcdefghijklm\nopq\rs\tuvwxyz");

strcmp('abcdefghijklm

s uvwxyz', 'abcdefghijklm

s uvwxyz')

=====================================================================

SELECT LENGTH('\\');

char_length('\')

===================

Example 2

The following is the result of executing Escape if a value for the system parameter ansi_quotes in the cubrid.conf file is yes, and a value for no_backslash_escapes is yes.

SELECT STRCMP('single quotes test('')', 'single quotes test(\')');

In the command from line 2,

ERROR: unterminated string

In the command from line 2,

ERROR: syntax error, unexpected UNTERMINATED_STRING

SELECT STRCMP("\a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z", "a\bcdefghijklm\nopq\rs\tuvwxyz");

In line 1, column 18,

ERROR: [\a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z] is not defined.

In line 1, column 18,

ERROR: [a\bcdefghijklm\nopq\rs\tuvwxyz] is not defined.

SELECT LENGTH('\\');

char_length('\\')

====================

Example 3

The following is the result of executing Escape if a value for the system parameter ansi_quotes in the cubrid.conf file is yes, and a value for no_backslash_escapes is no.

CREATE TABLE t1 (a varchar(200));

INSERT INTO t1 VALUES ('aaabbb'), ('aaa%');

SELECT a FROM t1 WHERE a LIKE 'aaa\%' escape '\\';

======================

'aaa%'

Character Strings-Definition and Characteristics

2012-04-19T03:36:34-07:00

Definition and Characteristics

Definition

CUBRID supports the following four types of character strings:

Fixed-length character string: CHAR(n)
Variable-length character string: VARCHAR(n)
Fixed-length national character string: NCHAR(n)
Variable-length national character string: NCHAR VARYING(n)

The followings are the rules that are applied when using the character string types.

In general, single quotations are used to enclose character string. Double quotations may be used as well depending on the value of ansi_quotes, which is a parameter related to SQL statement. If the ansi_quotes value is set to no, character string enclosed by double quotations is handled as character string, not as an identifier. The default value is yes. For details, Statement/Type-Related Parameters.
If there are characters that can be considered to be blank (e.g. spaces, tabs, or line breaks) between two character strings, these two character strings are treated as one according to ANSI standard. For example, the following example shows that a line break exists between two character string.
'abc'
'def'
The two strings above are considered identical to one string below.
'abcdef'
If you want to include a single quote as part of a character string, enter two single quotes in a row. For example, the character string on the left is stored as the one on the right.
''abcde''fghij' 'abcde'fghij
The maximum size of the token for all the character strings is 16 KB.
National character strings are used to store national (except English alphabet) character strings in a multilingual environment. Note that N (uppercase) should be followed by a single quote which encloses character strings.
N'Härder'

Characteristics

Length

For a CHAR or VARCHAR type, specify the length (bytes) of a character string for a NCHAR or NCHAR VARYING type, specify the number of character strings (number of characters).

When the length of the character string entered exceeds the length specified, the characters in excess of the specified length are truncated.

For a fixed-length character string type such as CHAR or NCHAR, the length is fixed at the declared length. Therefore, the right part (trailing space) of the character string is filled with space characters when the string is stored. For a variable-length character string type such as VARCHAR or NCHAR VARYING, only the entered character string is stored, and the space is not filled with space characters.

The maximum length of a CHAR or VARCHAR type to be specified is 1,073,741,823 the maximum length of a NCHAR or NCHAR VARYING type to be specified is 536,870,911. The maximum length that can be input or output in a CSQL statement is 8,192 KB.

Character Set, charset

A character set (charset) is a set in which rules are defined that relate to what kind of codes can be used for encoding when specified characters (symbols) are stored in the computer.

CUBRID supports the following character sets and you can specify them as the CUBRID_LANG environment variable. You can store data in other character sets (e.g. utf-8), but string function or LIKE search are not supported.

Character Set	CUBRID_LANG
8-bits ISO 8859-1 Latin	en_US
KSC 5601-1992 (EUC-KR)	ko_KR.euckr

Any characters from the above character sets can be included in a character string (the NULL character is represented as '\0').

Collating Character Sets

A collation is a set of rules used for comparing characters to search or sort values stored in the database when a certain character set is specified. Therefore, such rules are applied only to character string data types such as CHAR or VARCHAR. For a national character string type such as NCAHR() or NCHAR VARYING(), the sorting rules are determined according to the encoding algorithm of the specified character set.

Character String Coercion

Automatic coercion takes place between a fixed-length and a variable-length character string for the comparison of two characters, applicable only to characters that belong to the same character set. For example, when you extract a column value from a CHAR(5) data type and insert it into a column with a CHAR(10) data type, the data type is automatically coerced to CHAR(10). If you want to coerce a character string explicitly, use the CAST operator (See CAST Operator).

Character Strings

2012-04-19T03:36:34-07:00

Character Strings

Caution

2012-04-19T03:37:00-07:00

Caution

Returning Value of Java Stored Function/Procedure and Precision Type on IN/OUT

To limit the return value of Java stored function/procedure and precision type on IN/OUT, CUBRID processes as follows:

Checks the sql_type of the Java stored function/procedure.

Passes the value returned by Java to the database with only the type converted if necessary, ignoring the number of digits defined during creating the Java stored function/procedure. In principle, the user manipulates the passed data directly in the database.

Take a look at the following typestring() Java stored function.

public class JavaSP1{

public static String typestring(){

String temp = " ";

for(int i=0 i< 1 i++)

temp = temp + "1234567890";

return temp;

}

create function typestring() return char(5)

as language java

name 'JavaSP1.typestring() return java.lang.String';

Call typestring()

Result

======================

' 1234567890'

Returning java.sql.ResultSet in Java Stored Procedure

In CUBRID, you must use CURSOR as the data type when you declare a Java stored function/procedure that returns a java.sql.ResultSet.

create function rset() return cursor

as language java

name 'JavaSP2.TResultSet() return java.sql.ResultSet'

Before the Java file returns java.sql.ResultSet, it is required to cast to the CUBRIDResultSet class and then to call the setReturnable() method.

import cubrid.jdbc.driver.*;

import java.sql.*;

public class JavaSP2 {

public static ResultSet TResultSet(){

try{

Class.forName("cubrid.jdbc.driver.CUBRIDDriver");

Connection conn = DriverManager.getConnection("jdbc:default:connection:");

((CUBRIDConnection)conn).setCharset("euc_kr");

String sql = "select * from station";

Statement stmt=conn.createStatement();

ResultSet rs = stmt.executeQuery(sql);

((CUBRIDResultSet)rs).setReturnable();

return rs;

} catch (Exception e) {

e.printStackTrace();

}

return null;

}

In the calling block, you must set the OUT argument with Types.JAVA_OBJECT, get the argument to the getObject() function, and then cast it to the java.sql.ResultSet type before you use it. In addition, the java.sql.ResultSet is only available to use in CallableStatement of JDBC.

import java.sql.*;

public class TestResultSet{

public static void main(String[] args) {

Connnection conn = null;

Statement stmt= null;

int result;

int i;

try{

Class.forName("cubrid.jdbc.driver.CUBRIDDriver");

conn = DriverManager.getConnection("jdbc:CUBRID:localhost:33000:demodb:::","","");

CallableStatement cstmt = con.prepareCall("?=CALL rset()");

cstmt.registerOutParameter(1, Types.JAVA_OBJECT);

cstmt.execute();

ResultSet rs = (ResultSet) cstmt.getObject(1);

while(rs.next()) {

System.out.println(rs.getString(1));

}

rs.close();

} catch (Exception e) {

e.printStackTrace();

}

You cannot use the ResultSet as an input argument. If you pass it to an IN argument, an error occurs. An error also occurs when calling a function that returns ResultSet in a non-Java environment.

IN/OUT of Set Type in Java Stored Function/Procedure

If the set type of the Java stored function/procedure in CUBRID is IN OUT, the value of the argument changed in Java must be applied to IN OUT. When the set type is passed to the OUT argument, it must be passed as a two-dimensional array.

Create procedure setoid(x in out set, z object)

as language java name

'SetOIDTest.SetOID(cubrid.sql.CUBRIDOID[][], cubrid.sql.CUBRIDOID';

public static void SetOID(cubrid.sql.CUBRID[][] set, cubrid.sql.CUBRIDOID aoid){

Connection conn=null;

Statement stmt=null;

String ret="";

Vector v = new Vector();

cubrid.sql.CUBRIDOID[] set1 = set[0];

try {

if(set1!=null) {

int len = set1.length;

int i = 0;

for (i=0 i< len i++)

v.add(set1[i]);

}

v.add(aoid);

set[0]=(cubrid.sql.CUBRIDOID[]) v.toArray(new cubrid.sql.CUBRIDOID[]{});

} catch(Exception e) {

e.printStackTrace();

System.err.pirntln("SQLException:"+e.getMessage());

}

Using OID in Java Stored Function/Procedure

In case of using the OID type value for IN/OUT in CUBRID, use the value passed from the server.

create procedure tOID(i inout object, q string)

as language java

name 'OIDtest.tOID(cubrid.sql.CUBRIDOID[], java.lang.String)';

public static void tOID(CUBRIDOID[] oid, String query)

{

Connection conn=null;

Statement stmt=null;

String ret="";

try {

Class.forName("cubrid.jdbc.driver.CUBRIDDriver");

conn=DriverManager.getConnection("jdbc:default:connection:");

conn.setAutoCommit(false);

stmt = conn.createStatement();

ResultSet rs = stmt.executeQuery(query);

System.out.println("query:"+ query);

while(rs.next()) {

oid[0]=(CUBRIDOID)rs.getObject(1);

System.out.println("oid:"+oid[0].getTableName());

}

stmt.close();

conn.close();

} catch (SQLException e) {

e.printStackTrace();

System.err.println("SQLException:"+e.getMessage());

} catch (Exception e) {

e.printStackTrace();

system.err.println("Exception:"+ e.getMessage());

}

Environment Configuration for Java Stored Function|Procedure

2012-04-19T03:36:59-07:00

Environment Configuration for Java Stored Function/Procedure

To use Java-stored functions/procedures in CUBRID, you must have JRE (Java Runtime Environment) 1.6 or better installed in the environment where the CUBRID server is installed. You can download JRE from the Developer Resources for Java Technology (http://java.sun.com).

If the java_stored_procedure parameter in the CUBRID configuration file (cubrid.conf) is set to yes, CUBRID 64-bit needs a 64-bit Java Runtime Environment, and CUBRID 32-bit needs a 32-bit Java Runtime Environment. For example, when you run CUBRID 64-bit in the system in which a 32-bit JAVA Runtime Environment is installed, the following error may occur.

% cubrid server start demodb

This may take a long time depending on the amount of recovery works to do.

WARNING: Java VM library is not found : /usr/java/jdk1.6.0_15/jre/lib/amd64/server/libjvm.so: cannot open shared object file: No such file or directory.

Consequently, calling java stored procedure is not allowed

Execute the following command to check the JRE version if you have it already installed in the system.

% java -version Java(TM) SE Runtime Environment (build 1.6.0_05-b13)

Java HotSpot(TM) 64-Bit Server VM (build 10.0-b19, mixed mode)

Windows Environment

For Windows, CUBRID loads the jvm.dll file to run the Java Virtual Machine. CUBRID first locates the jvm.dll file from the PATH environment variable and then loads it. If it cannot find the file, it uses the Java runtime information registered in the system registry.

You can configure the JAVA_HOME environment variable and add the directory in which the Java executable file is located to Path, by executing the command as follows: For information on configuring environment variables using GUI, see Setting up the JDBC Environment.

An example of installing 64 Bit JDK 1.6 and configuring the environment variables
% set JAVA_HOME=C:\jdk1.6.0
% set PATH=%PATH%;%JAVA_HOME%\jre\bin\server
An example of installing 32 Bit JDK 1.6 and configuring the environment variables
% set JAVA_HOME=C:jdk1.6.0
% set PATH=%PATH%;%JAVA_HOME%\jre\bin\client

To use other vendor's implementation instead of Sun's Java Virtual Machine, add the path of the jvm.dll file to the PATH variable during the installation.

Linux/UNIX Environment

For Linux/UNIX environment, CUBRID loads the libjvm.so file to run the Java Virtual Machine. CUBRID first locates the libjvm.so file from the LD_LIBRARY_PATH environment variable and then loads it. If it cannot find the file, it uses the JAVA_HOME environment variable. For Linux, glibc version 2.3.4 or higher is supported. The following example shows how to configure the Linux environment variable (e.g., .profile, .cshrc, .bashrc, .bash_profile, etc.).

An example of installing 64 Bit JDK 1.6 and configuring the environment variables in a bash shell
% JAVA_HOME=/usr/java/jdk1.6.0_10
% LD_LIBRARY_PATH=$JAVA_HOME/jre/lib/amd64:$JAVA_HOME/jre/lib/amd64/server:$LD_LIBRARY_PATH
% export JAVA_HOME
% export LD_LIBRARY_PATH
An example of installing 32 Bit JDK 1.6 and configuring the environment variables in a bash shell
% JAVA_HOME=/usr/java/jdk1.6.0_10
% LD_LIBRARY_PATH=$JAVA_HOME/jre/lib/i386/:$JAVA_HOME/jre/lib/i386/client:$LD_LIBRARY_PATH
% export JAVA_HOME
% export LD_LIBRARY_PATH
An example of installing 64 Bit JDK 1.6 and configuring the environment variables in a csh
% setenv JAVA_HOME /usr/java/jdk1.6.0_10
% setenv LD_LIBRARY_PATH $JAVA_HOME/jre/lib/amd64:$JAVA_HOME/jre/lib/amd64/server:$LD_LIBRARY_PATH
% set path=($path $JAVA_HOME/bin .)
An example of installing 32 Bit JDK 1.6 and configuring the environment variables in a csh shell
% setenv JAVA_HOME /usr/java/jdk1.6.0_10
% setenv LD_LIBRARY_PATH $JAVA_HOME/jre/lib/i386:$JAVA_HOME/jre/lib/i386/client:$LD_LIBRARY_PATH
% set path=($path $JAVA_HOME/bin .)

To use other vendor's implementation instead of Sun's Java Virtual Machine, add the path of the JVM (libjvm.so) to the library path during the installation.

The path of the libjvm.so file can be different depending on the platform. For example, the path is the $JAVA_HOME/jre/lib/sparc directory in a SUN Sparc machine.

Writing CCI Program

2012-04-19T03:37:21-07:00

Writing CCI Application Program

The basic steps used for writing programs are as follows, and a step for binding the data to a variable is added to use the prepared statement. The steps are implemented in example codes 1 and 2.

You can configure the default value of auto-commit mode by using CCI_DEFAULT_AUTOCOMMIT (broker parameter) upon startup of an application. If configuration on broker parameter is omitted, the default value is ON; use the cci_set_autocommit() function to change auto-commit mode within an application. If auto-commit mode is OFF, you must explicitly commit or roll back transaction by using the cci_end_tran() function.

Opening a database connection handle (related functions : cci_connect(), cci_connect_with_url())
Preparing an SQL statement (related function : cci_prepare())
Binding data to a prepared SQL statement (related function : cci_bind_param())
Executing a prepared SQL statement (related function : cci_execute())
Processing the execution result (related functions : cci_cursor(), cci_fetch(), cci_get_data(), cci_get_result_info())
Closing the request handle (related function : cci_close_req_handle())
Closing a database connection handle (related function : cci_disconnect())
Using database connection pool (related functions : cci_property_create(), cci_property_destroy(), cci_property_set(), cci_datasource_create(), cci_datasource_destroy(), cci_datasource_borrow(), cci_datasource_release())

Example 1

//Example to execute a simple query

#include <stdio.h>

#include "cas_cci.h"

#define BUFSIZE (1024)

int

main (void)

{

int con = 0, req = 0, col_count = 0, i, ind;

int error;

char *data;

T_CCI_ERROR cci_error;

T_CCI_COL_INFO *col_info;

T_CCI_SQLX_CMD cmd_type;

char *query = "select * from code";

//getting a connection handle for a connection with a server

con = cci_connect ("localhost", 33000, "demodb", "dba", "");

if (con < 0)

{

printf ("cannot connect to database ");

return 1;

}

//preparing the SQL statement

req = cci_prepare (con, query, 0, &cci_error);

if (req < 0)

{

printf ("prepare error: %d, %s ", cci_error.err_code,

cci_error.err_msg);

goto handle_error;

}

//getting column information when the prepared statement is the SELECT query

col_info = cci_get_result_info (req, &cmd_type, &col_count);

if (col_info == NULL)

{

printf ("get_result_info error: %d, %s ", cci_error.err_code,

cci_error.err_msg);

goto handle_error;

}

//Executing the prepared SQL statement

error = cci_execute (req, 0, 0, &cci_error);

if (error < 0)

{

printf ("execute error: %d, %s ", cci_error.err_code,

cci_error.err_msg);

goto handle_error;

}

while (1)

{

//Moving the cursor to access a specific tuple of results

error = cci_cursor (req, 1, CCI_CURSOR_CURRENT, &cci_error);

if (error == CCI_ER_NO_MORE_DATA)

{

break;

}

if (error < 0)

{

printf ("cursor error: %d, %s ", cci_error.err_code,

cci_error.err_msg);

goto handle_error;

}

//Fetching the query result into a client buffer

error = cci_fetch (req, &cci_error);

if (error < 0)

{

printf ("fetch error: %d, %s ", cci_error.err_code,

cci_error.err_msg);

goto handle_error;

}

for (i = 1; i <= col_count; i++)

{

//Getting data from the fetched result

error = cci_get_data (req, i, CCI_A_TYPE_STR, &data, &ind);

if (error < 0)

{

printf ("get_data error: %d, %d ", error, i);

goto handle_error;

}

printf ("%s |", data);

}

printf (" ");

}

//Closing the request handle

error = cci_close_req_handle (req);

if (error < 0)

{

printf ("close_req_handle error: %d, %s ", cci_error.err_code,

cci_error.err_msg);

goto handle_error;

}

//Disconnecting with the server

error = cci_disconnect (con, &cci_error);

if (error < 0)

{

printf ("error: %d, %s ", cci_error.err_code, cci_error.err_msg);

goto handle_error;

}

return 0;

handle_error:

if (req > 0)

cci_close_req_handle (req);

if (con > 0)

cci_disconnect (con, &cci_error);

return 1;

}

Example 2

//Example to execute a query with a bind variable

char *query = "select * from nation where name = ?";

char namebuf[128];

//getting a connection handle for a connection with a server

con = cci_connect ("localhost", 33000, "demodb", "dba", "");

if (con < 0)

{

printf ("cannot connect to database ");

return 1;

}

//preparing the SQL statement

req = cci_prepare (con, query, 0, &cci_error);

if (req < 0)

{

printf ("prepare error: %d, %s ", cci_error.err_code,

cci_error.err_msg);

goto handle_error;

}

//Binding date into a value

strcpy (namebuf, "Korea");

error =

cci_bind_param (req, 1, CCI_A_TYPE_STR, &namebuf, CCI_U_TYPE_STRING,

CCI_BIND_PTR);

if (error < 0)

{

printf ("bind_param error: %d ", error);

goto handle_error;

}

Example 3

#include <stdio.h>

#include "cas_cci.h"

//Example to use connection/statement pool in CCI

int main ()

{

T_CCI_PROPERTIES *ps = NULL;

T_CCI_DATASOURCE *ds = NULL;

T_CCI_ERROR err;

T_CCI_CONN cons[20];

int rc = 1, i;

ps = cci_property_create ();

if (ps == NULL)

{

fprintf (stderr, "Could not create T_CCI_PROPERTIES. ");

rc = 0;

goto cci_pool_end;

}

cci_property_set (ps, "user", "dba");

cci_property_set (ps, "url", "cci:cubrid:localhost:33000:demodb:::");

cci_property_set (ps, "pool_size", "10");

cci_property_set (ps, "max_wait", "1200");

cci_property_set (ps, "pool_prepared_statement", "true");

cci_property_set (ps, "default_autocommit", "false");

cci_property_set (ps, "default_isolation", "TRAN_REP_CLASS_UNCOMMIT_INSTANCE");

cci_property_set (ps, "default_lock_timeout", "10");

cci_property_set (ps, "login_timeout", "300000");

cci_property_set (ps, "query_timeout", "3000");

ds = cci_datasource_create (ps, &err);

if (ds == NULL)

{

fprintf (stderr, "Could not create T_CCI_DATASOURCE. ");

fprintf (stderr, "E[%d,%s] ", err.err_code, err.err_msg);

rc = 0;

goto cci_pool_end;

}

for (i = 0; i < 3; i++)

{

cons[i] = cci_datasource_borrow (ds, &err);

if (cons[i] < 0)

{

fprintf (stderr,

"Could not borrow a connection from the data source. ");

fprintf (stderr, "E[%d,%s] ", err.err_code, err.err_msg);

continue;

}

// put working code here.

cci_work (cons[i]);

}

sleep (1);

for (i = 0; i < 3; i++)

{

if (cons[i] < 0)

{

continue;

}

cci_datasource_release (ds, cons[i], &err);

}

cci_pool_end:

cci_property_destroy (ps);

cci_datasource_destroy (ds);

return 0;

}

// working code

int cci_work (T_CCI_CONN con)

{

T_CCI_ERROR err;

char sql[4096];

int req, res, error, ind;

int data;

cci_set_autocommit (con, CCI_AUTOCOMMIT_TRUE);

cci_set_lock_timeout (con, 100, &err);

cci_set_isolation_level (con, TRAN_REP_CLASS_COMMIT_INSTANCE, &err);

error = 0;

snprintf (sql, 4096, "SELECT host_year FROM record WHERE athlete_code=11744");

req = cci_prepare (con, sql, 0, &err);

if (req < 0)

{

printf ("prepare error: %d, %s ", err.err_code, err.err_msg);

return error;

}

res = cci_execute (req, 0, 0, &err);

if (res < 0)

{

printf ("execute error: %d, %s ", err.err_code, err.err_msg);

goto cci_work_end;

}

while (1)

{

error = cci_cursor (req, 1, CCI_CURSOR_CURRENT, &err);

if (error == CCI_ER_NO_MORE_DATA)

{

break;

}

if (error < 0)

{

printf ("cursor error: %d, %s ", err.err_code, err.err_msg);

goto cci_work_end;

}

error = cci_fetch (req, &err);

if (error < 0)

{

printf ("fetch error: %d, %s ", err.err_code, err.err_msg);

goto cci_work_end;

}

error = cci_get_data (req, 1, CCI_A_TYPE_INT, &data, &ind);

if (error < 0)

{

printf ("get data error: %d ", error);

goto cci_work_end;

}

printf ("%d ", data);

}

error = 1;

cci_work_end:

cci_close_req_handle (req);

return error;

}

Changing Database Information of CM Users

2012-04-19T03:37:31-07:00

Changing Database Information of CM Users

Description

The cm_admin changedbinfo utility changes database information of specified CM users.

Syntax

cm_admin changedbinfo options cmuser-name database-name

options :

[{-u | --uid} userid]

[{-h | --host} broker-ip]

[{-p | --port} broker-port]

cm_admin : An integrated utility to manage CUBRID Manager
changedbinfo : The command used to change database information of a specified CM user.
options : The -u, -h, and –p options are supported. For details, see its description and example.
cmuser-name : The name of a CM user
databse-name : The name of a database to be changed.

Options

Option	Description
-u --uid	Specifies the user ID of a database.
-h --host	Specifies the host of a broker used when client can accesses a database.
-p --port	Specifies the port number of a broker used when client accesses a database.

Changing database user ID (-u)

The following example shows how to update ID information in the database "testdb" of a CM user "testcm" to "uid".

cm_admin changedbinfo -u uid testcm testdb

Changing host IP of a broker (-h)

The following example shows how to update host IP information in the database "testdb" of a CM user "testcm" to "10.34.63.132".

cm_admin changedbinfo -h 10.34.63.132 testcm testdb

Changing broker port (-u)

The following example shows how to update broker port information in the database "testdb" of a CM user "testcm" to "33000".

cm_admin changedbinfo -p 33000 testcm testdb

Adding Database Information to CM Users

2012-04-19T03:37:31-07:00

Adding Database Information to CM Users

Description

The cm_admin adddbinfo utility adds database information (database name, UID, broker IP, borker port) to CM users.

Syntax

cm_admin adddbinfo options cmuser-name database-name

options :

[{-u | --uid} userid]

[{-h | --host} broker-ip]

[{-p | --port} broker-port]

cm_admin : An integrated utility to manage CUBRID Manager
adddbinfo : The command used to add database information to a CM user
options: The -u, -h, and –p options are supported. For details, see its description and example.
cmuser-name : The name of a CM user
databse-name: The name of a database to be added

Options

Option	Description
-u --uid	Specifies the user ID of a database (default value : dba).
-h --host	Specifies the host of a broker used when client accesses a database (default value : localhost).
-p --port	Specifies the port number of a broker used when client accesses a database (default value : 30000).

Adding database user ID (-u)

The following example shows how to add a database "testdb" and its user id "uid" to a CM user named "testcm".

cm_admin adddbinfo -u uid testcm testdb

Adding host IP of broker (-h)

The following example shows how to add a database "testdb" and its host IP "127.0.0.1" to a CM user named "testcm".

cm_admin adddbinfo -h 127.0.0.1 testcm testdb

Adding broker port (-u)

The following example shows how to add a database "testdb" and its broker port to "33000" to a CM user named "testcm".

cm_admin adddbinfo -p 33000 testcm testdb

Creating a default database

The following example shows how to add a default database "testdb" to a CM user named "testcm".

cm_admin adddbinfo testcm testdb

Deleting Database Information from CM Users

2012-04-19T03:37:31-07:00

Deleting Database Information from CM Users

Description

The cm_admin deldbinfo utility deletes database information from specified CM users.

Syntax

cm_admin deldbinfo cmuser-name database-name

cm_admin : An integrated utility to manage CUBRID Manager
deldbinfo : The command used to delete database information from a specified CM user
cmuser-name : The name of a CM user
database-name : The name of a database to be deleted

Example

The following example shows how to delete information of a database "testdb" from a CM user "testcm".

cm_admin deldbinfo testcm testdb

Logs

2012-04-19T03:37:31-07:00

Logs

Logs consist of Broker, Manager and Database logs. There can be sub-nodes such as Access, Error and Admin logs. Each log consists as follows:

Broker Log

Access Log

The access log file records information about application client access, and it analyzes and outputs what is saved with the name of " broker_name.access." In addition, if the LOG_BACKUP parameter is configured to " ON" in the Broker configuration file (cubrid_broker.conf), the information about the termination date and time is stored additionally to the log file upon successful termination of the broker operation.

Error Log

The error log file records information about errors that occurred during the client's request processing and is saved with the name of " broker_name_app_server_num.err."

The following example and description shows an error log.

Time: 02/04/09 13:45:17.687 - SYNTAX ERROR *** ERROR CODE = -493, Tran = 1, EID = 38

Syntax: Unknown class " unknown_tbl" . select * from unknown_tbl

Time : 02/04/09 13:45:17.687 : Time when the error occurred
SYNTAX ERROR : Type of the error (SYNTAX ERROR, ERROR, etc.)
*** ERROR CODE = -493 : Error code
Tran = 1 : Transaction ID. -1 if no transaction ID is assigned.
EID = 38 : Error ID. This ID is used to find the SQL log related to the server or client logs when an error occurs during SQL statement processing.

Error Log Trace

You also can trace the broker error log for SYNTAX ERROR Type.

Click the [Trace Error] action, will pop up the error trace result dialog.

Admin Log

The admin log records the history about the service operation and termination.

Manager Log

Access Log

The access log files records information about the CUBRID Manager access. You can see user accounts, operation history, and time when operations are performed.

Error Log

The error log file records information about errors that occurred while connecting the CUBRID Manager.

Database Log

Admin Log

This admin log records information about errors that occurred while server is running. The format of output file is as follows: < database_name> _< date> _< time> .err.

CUBRID Manager Administrator Guide

2012-04-19T03:37:31-07:00

CUBRID Manager Administrator’s Guide

As a CLI tool to help you manage users in CUBRID Manager, CUBRID Manager Administrator is supported for Linux only. This chapter explains how to users of CUBRID Manager Administrator.

This chapter includes the following sections:

How to use the utilities of CUBRID Manager Administrator
How to use the utilities of CUBRID Manager Administrator
CM Users
Adding CM users
Deleting CM users
Displaying information of CM users
Changing the authority of CM users
Changing the passwords of CM users
Adding database Information to CM users
Deleting database Information from CM users
Changing database Information of CM users

CUBRID Manager Administrator Utilities

2012-04-19T03:37:31-07:00

CUBRID Manager Administrator Utilities

CUBRID Manager Administrator utilities provide features that can be used to manage the CUBRID Manager services. It is supported for Linux only, and so far it provides the operations on CM users (database administrators; it means the users of CUBRID Manager in this context) information.

The management utilities are as follows:

CM user add/delete/view/ utility
- cm_admin adduser
- cm_admin deluser
- cm_admin viewuser
CM User change authority/ change password/ add database info/ change database info/ delete database information utility.
- cm_admin changeuserauth
- cm_admin changeuserpwd
- cm_admin adddbinfo
- cm_admin changedbinfo
- cm_admin deldbinfo

The following information will be displayed upon entering cm_admin in a prompt.

cmserver utility, version R0.1

usage: cm_admin <utility-name> [args]

Available Utilities:

adduser

deluser

viewuser

changeuserauth

changeuserpwd

adddbinfo

deldbinfo

changedbinfo

How to Use CUBRID Manager Administrator Utilities

2012-04-19T03:37:31-07:00

How to Use Utilities of CUBRID Manager Administrator

The following syntax shows how to use utilities of CUBRID Manager Administrator.

cm_admin utility_name

utility_name:

adduser [option] <cmuser-name> <cmuser-password> --- Adding CM users

deluser <cmuser-name> --- Deleting CM users

viewuser [cmuser-name] --- Displaying CM information

changeuserauth [option] <cmuser-name> --- Changing the authorization of CM users

changeuserpwd [option] <cmuser-name> --- Changing the passwords of CM users

adddbinfo [option] <cmuser-name> <database-name> --- Adding database information of CM users

deldbinfo <cmuser-name> <database-name> --- Deleting database information of CM users

changedbinfo [option] <database-name> number-of-pages --- Changing database information of CM users

CM Users

2012-04-19T03:37:31-07:00

CM Users

Information of CM (CUBRID Manager) users consists of the following parts:

CM user authority includes the followings:
- Broker authority
- Database creation authority; currently only "admin" user can have this authority
- Status monitoring authority

Database information : The databases that CM users can use
CM user password : The passwords of CM users

The default user of CUBRID Manager have an admin account which provides all the authorities of management (password : admin).

Adding CM Users

2012-04-19T03:37:31-07:00

Adding CM Users

Description

The cm_admin adduser utility creates CM users who have specific authority and database information. The authority to configure broker privilege, create database, and monitor status) can be granted to CM users.

Syntax

cm_admin adduser options cmuser-name cmuser-password

options :

[{-b | --broker } authority]

[{-c | --dbcreate } authority]

[{-m | --monitor} authority]

[{-d | --dbinfo} database-info]

cm_admin : An integrated utility to manage CUBRID Manager
adduser : The command used to create a new CM user
options : The -b, -c, -m, and –d options are supported. For details, see its description and example.
cmuser-name : Specifies a unique name of a CM user to be created. The name should have at least 4 characters in length. If the specified cmuser-name is the same as the existing one, cm_admin halts the creation of a CM user.
cmuser-password : The password of a CM user. The password should have be at least 4 characters in length.

Options

Option	Description
-b --broker	Specifies the broker authority of a CM user to be created. - Value available : admin, none, monitor - Default value : none
-c --dbcreate	Specifies the database creation authority of a CM user to be created. - Value available : none, admin - Default value : none
-m --monitor	Specifies the monitoring authority of a CM user to be created. - Value available : admin, none, monitor - Default value : none
-d --dbinfo	Specifies the database information of a CM user to be created. The format of DBINFO should be as follows: "<dbname>;<uid>;<broker_ip>,<broker_port>"

Configuring broker authority (-b)

The following example shows how to create a CM user "testcm" and its password "testcmpwd", and configure the value of broker authority to monitor.

cm_admin adduser -b monitor testcm testcmpwd

Configuring database creation authority (-c)

The following example shows how to create a CM user "testcm" and its password "testcmpwd", and configure the value of database creation authority to admin.

cm_admin adduser -c admin testcm testcmpwd

Configuring status monitoring authority (-m)

The following example shows how to create a CM user "testcm" and its password "testcmpwd", and configure the value of its status monitoring authority to admin.

cm_admin adduser -m admin testcm testcmpwd

Adding database information (-d)

The following example shows how to add database information "testdb;dba;localhost,30000" to a CM user "testcm".

cm_admin adduser -d "testdb;dba;localhost,30000" testcm testcmpwd

Deleting CM Users

2012-04-19T03:37:31-07:00

Deleting CM Users

Description

The cm_admin deluser utility deletes CM users based on the given CM user name.

Syntax

cm_admin deluser cmuser-name cmuser-password

cm_admin : An integrated utility to manage CUBRID Manager
deluser : The command used to create an existing CM user
cmuser-name : The name of a CM user to be deleted

Deleting CM User

The following example shows how to delete a CM user "testcm".

cm_admin deluser testcm

Displaying CM User Information

2012-04-19T03:37:31-07:00

Displaying Information of CM Users

Description

The cm_admin viewuser utility displays information of CM users.

Syntax

cm_admin viewuser cmuser-name

cm_admin : An integrated utility to manage CUBRID Manager
viewuser : The command used to display authority and database information of a CM user.
cmuser-name : The name of a user. If this value is specified, only the corresponding user's information will be displayed; if it is omitted, all existing CM user's information will be displayed.

Example

The following example shows how to display information of a CM user "testcm".

cm_admin viewuser testcm

The following information will be displayed.

CM USER: testcm

Auth info:

broker: none

dbcreate: none

statusmonitorauth: none

DB info:

==========================================================================================

DBNAME UID BROKER INFO

==========================================================================================

testdb dba localhost,30000

Changing the Authority of CM Users

2012-04-19T03:37:31-07:00

Changing the Authority of CM Users

Description

The cm_admin changeuserauth utility changes authority of CM users.

Syntax

cm_admin changeuserauth options cmuser-name

options :

[{-b | --broker} authority]

[{-c | --dbcreate} authority]

[{-m | --monitor} authority]

cm_admin : An integrated utility to manage CUBRID Manager
changeuserauth: The command used to change the authority information of a CM user
options : The -b, -c, and -m options are supported. For details, see its description and example.
cmuser-name : The name of a CM user whose authority to be changed.

Options

Option	Description
-b --broker	Specifies the broker authority of a CM user. - Value available : admin, none, monitor
-c --dbcreate	Specifies the database creation authority of a CM user. - Value available : none, admin
-m --monitor	Specifies the monitoring authority of a CM user. - Value available : admin, none, monitor

Changing broker authority (-b)

The following example shows how to change the broker authority of a CM user "testcm" to monitor.

cm_admin changeuserauth -b monitor testcm

Changing database creation authority (-c)

The following example shows how to change database creation authority of a CM user "testcm" to admin.

cm_admin changeuserauth -c admin testcm

Changing status monitoring authority (-m)

The following example shows how to change status monitoring authority of a CM user "testcm" to admin.

cm_admin changeuserauth -m admin testcm