Skip to end of metadata
Go to start of metadata

 

Overview


This document explains the interfaces provided by Altibase.

 

Version


All the versions of Altibase HDB

 

Interface provided by Altibase


  • Altibase complies with the international standard ANSI SQL-1999 and provides various standard interfaces such as ODBC, ADO. Net, JDBC, and Embedded SQL.

 

Client development environment

Interface typeSupport function

ODBC

  • RAD (Rapid Application Development) tools such as Visual Basic and PowerBuilder, as well as used when accessing ALTIBASE in most development environments
  • Reinforced standard support with re-implementation

JDBC

  • Used when developing ALTIBASE application programs in JAVA environment

  • Also used when configuring a connection pool in WAS

  • Improved performance with re-implementation

  • JDBC 2.0 API support up to Altibase 6.1.1, JDBC 3.0 API support partially.

  • JDBC 3.0 API support from Altibase 6.3.1.

SQLCLI

  • ALTIBASE's low-level API based on C language

  • Provide LOB API, ALA (ALTIBASE Log Analyzer) API, ACS (ALTIBASE Call-Level for Spatial) API

Embedded

SQL (Pre-Compiler)

  • Interface used by the host language of C or C++

  • Improved development productivity by using SQL statements as they are in the host language

ADO.NET

  • Common programming interface to access database data based on Windows .Net Framework

Unix ODBC

  • Standard DB connection API compatible with Windows ODBC source on Unix
  • Provide compatibility with ETL tools such as DataStage and Informatica and OLAP tools such as MSTR and Sagent

Server development environment

FunctionCharacterstic

SQL

  • Support Full Featured SQL92
  • Support international standard complex query such as Sub Query INLINE view

Built-in Function

  • Provides more than 100 built-in functions

  • Users can perform various operations in SQL statements by using Built-in Function

Stored Procedure & Function

  • Support Stored Procedure and Stored Function based on ANSI SQL standard

  • Result Set can be sent to the client in the procedure

  • Support structured type and array type within procedure

  • Support Dynamic SQL/DDL within the procedure

View

  • Efficiently query by unioning multiple tables or creating a specific SQL as a view

Trigger

  • Support Trigger by standard for business function in the form of data events

  • Support Update Trigger for a specific column

 

 

  • No labels