iusql(1) [centos man page]
isql(1) UnixODBC manual pages isql(1) NAME
isql, iusql - unixODBC command-line interactive SQL tool SYNOPSIS
isql DSN [USER [PASSWORD]] [options] DESCRIPTION
isql is a command line tool which allows the user to execute SQL in batch or interactively. It has some interesting options such as an option to generate output wrapped in an HTML table. iusql is the same tool with built-in Unicode support. ARGUMENTS
DSN The Data Source Name, which should be used to make connection to the database. The data source is looked for in the /etc/odbc.ini and $HOME/.odbc.ini files in that order, with the latter overwriting the former. USER Specifies the database user/role under which the connection should be made. PASSWORD Password for the specified USER. OPTIONS
-b Run isql in non-interactive batch mode. In this mode, the isql processes its standard input, expecting one SQL command per line. -dDELIMITER Delimits columns with delimiter. -xHEX Delimits columns with HEX, which is a hexadecimal code of the delimiting character in the format 0xNN - i.e. 0x09 for the TAB char- acter. -w Format the result as HTML table. -c Output the names of the columns on the first row. Has any effect only with the -d or -x options. -mNUM Limit the column display width to NUM characters. -lLOCALE Sets locale to LOCALE. -q Wrap the character fields in double quotes. -3 Use the ODBC 3 calls. -n Use the newline processing. -e Use the SQLExecDirect instead of Prepare. -k Use SQLDriverConnect. -v Turn on the verbose mode, where the errors are fully described. Useful for debugging. --version Prints the program version and exits. COMMANDS
This section briefly describes some isql runtime commands. help List all tables in the database. help table List all columns in the table. help help List all help options. EXAMPLES
$ isql WebDB MyID MyPWD -w -b < My.sql Connects to the WebDB as user MyID with password MyPWD, then execute the commands in the My.sql file and returns the results wrapped in HTML table. Each line in My.sql must contain exactly 1 SQL command, except for the last line, which must be blank (unless the -n option is specified). FILES
/etc/odbc.ini System-wide DSN definitions. See odbc.ini(5) for details. $HOME/.odbc.ini User-specific DSN definitions. See odbc.ini(5) for details. SEE ALSO
odbcinst(1), odbc.ini(5) AUTHORS
The authors of unixODBC are Peter Harvey <pharvey@codebydesign.com> and Nick Gorham <nick@easysoft.com>. For the full list of contributors see the AUTHORS file. COPYRIGHT
unixODBC is licensed under the GNU Lesser General Public License. For details about the license, see the COPYING file. version 2.3.1 Tue 25 Jun 2013 isql(1)
Check Out this Related Man Page
iodbctest(1) iODBC Driver Manager iodbctest(1) NAME
iodbctest, iodbctestw - iODBC Demonstration programs SYNOPSIS
iodbctest ["DSN=xxxx[;UID=xxxx][;PWD=xxxx][;OPT=value]"] iodbctestw ["DSN=xxxx[;UID=xxxx][;PWD=xxxx][;OPT=value]"] DESCRIPTION
The iodbctest program and iodbtestw programs are simple ODBC sample programs, showing the strength of the ODBC API to connect to any ODBC enabled database, issue SQL commands and retrieve the query results. The iodbctest program uses the standard ODBC API calls to connect using any DSN, but retrieves all results in ASCII mode. The iodbctestw program uses the ODBC Unicode API calls to connect using any DSN, and retrieves all results in Unicode mode. OPTIONS
The iodbctest program uses the SQLDriverConnect function to make a connection using any available ODBC compliant driver. This allows the user to override any ODBC connect attribute in the DSN string. Connect strings should start with either a DSN=xxx or a DRIVER=xxxx attribute optionally followed by other DSN attributes separated by a semicolon e.g: DSN=ora9;UID=scott;PWD=tiger;DATABASE=ora9u Any attributes required for a proper connection that are not entered in the DSN connect string, must be present in the odbc.ini file. If the connect string is passed as an argument to the iodbctest program, the string should be quoted as most shells use the semicolon as their command separator. If the connect string is entered on the interactive prompt, no quotes should be used. After a successful connection has been established, the user is prompted for a SQL command to be send to the database. A SQL command cannot span multiple lines. If the SQL command returns one or more result sets, each result set is fetched using character buffers and displayed in a table. Additionally, the iodbctest program understands a few special commands: qualifiers Show a list of qualifiers using the SQLTables catalog call. owners Show a list of owners using the SQLTables catalog call. tables Show a list of tables using the SQLTables catalog call. types Show a list of tables types using the SQLTables catalog call. datatypes Show a list of data types using the SQLGetTypeInfo catalog call. reconnect Perform a disconnect/reconnect with the information saved during the first SQLDriverConnect. quit (or exit) Exit the program and return to the shell. EXAMPLES
Start the iodbctest program and get a list of DSNs before making a connection: $ iodbctest OpenLink ODBC Demonstration program This program shows an interactive SQL processor Enter ODBC connect string (? shows list): ? DSN | Driver ----------------------------------------------------------------- ora9 | OpenLink Generic ODBC Driver mysql | OpenLink Generic ODBC Driver mysqllite | OpenLink Lite for MySQL myodbc | MyODBC Driver pgsql | OpenLink Generic ODBC Driver tds | OpenLink Generic ODBC Driver Enter ODBC connect string (? shows list): DSN=ora9;PWD=tiger Driver: 05.20.0316 OpenLink Generic ODBC Driver (oplodbc.so) SQL> Connect to an Oracle 9 instance which has been previously setup in the odbc.ini file: $ iodbctest "DSN=ora9;UID=scott;PWD=tiger" iODBC Demonstration program This program shows an interactive SQL processor Driver: 05.20.0316 OpenLink Generic ODBC Driver (oplodbc.so) SQL>select * from emp ID |NAME -----------------+------------------------------------------- 1 |Record 1 2 |Record 2 2 |Record 3 result set 1 returned 3 rows. SQL> quit COPYRIGHT
Copyright (C) 1996-2009 by OpenLink Software AUTHOR
iODBC Administrator <iodbc@openlinksw.com> 3.52.7 3 August 2005 iodbctest(1)