ns_db

Overview

Access the AOLserver database

Syntax

ns_db bindrow dbhandle

ns_db bouncepool dbhandle

ns_db cancel dbhandle

ns_db close dbhandle

ns_db connected dbhandle

ns_db datasource dbhandle

ns_db dbtype dbhandle

ns_db dml dbhandle sql

ns_db driver dbhandle

ns_db exception dbhandle

ns_db exec dbhandle sqlcommand

ns_db flush dbhandle

ns_db gethandle ?-timeout timeout? [poolname] nhandles

ns_db getrow dbhandle setId

ns_db open driver datasource user password

ns_db poolname dbhandle

ns_db pools

ns_db releasehandle dbhandle

ns_db 1row dbhandle sql

ns_db 0or1row dbhandle sql

ns_db password dbhandle

ns_db select dbhandle sql

ns_db setexception dbhandle code message

ns_db sp_exec dbhandle

ns_db sp_getparams

ns_db sp_returncode dbhandle

ns_db sp_setparam dbhandle varname vartype inout value

ns_db sp_start dbhandle procname

ns_db user dbhandle

ns_db verbose dbhandle ?on | off?

Description

ns_db bindrow returns an ns_set structure whose key names are the column names of the rows returned by the SQL command previously-executed with ns_db exec. If the database is not currently returning rows (i.e., a status other than NS_ROWS was returned by ns_db exec), an error is thrown. The dbhandle argument is a database handle (obtained with ns_db gethandle).

ns_db bouncepool marks all database handles for the specified database pool as stale. When any database handle currently open is put back into the pool, its connection to the database will be reset.

ns_db cancel cancels the current operation.

ns_db close closes the connection. Use this function only on handles that were obtained by the ns_db open function. However, the server automatically close handles when the operation is complete, so you don't normally have to call this function.

ns_db connected returns a boolean value indicating whether the connection to the database pool is made.

ns_db datasource returns the data source for the database pool (e.g., default:mydb).

ns_db dbtype returns the database type of the database pool.

ns_db dml executes SQL that should be data manipulation language such as an insert or update, or data definition language such as a create table.

ns_db driver returns the name of the driver of the handle (e.g., "SOLID").

ns_db exception returns the most recent exception for the database pool.

ns_db exec executes the specified SQL command. It returns either NS_DML (if the SQL command is a DML or DDL command) or NS_ROWS (if the SQL command returns rows, such as a SELECT). If an error occurs executing the SQL command, an error is thrown. The dbhandle argument is a database handle (obtained with ns_db gethandle). This function can be used for true ad hoc querying, where you don't know what kind of SQL command will be executed.

ns_db flush flushes the results of an SQL select so you do not need to use ns_db getrow to get all the rows and throw them away.

ns_db gethandle returns the specified number of handles from the specified pool. If poolname is not specified, the Defaultpool from the configuration file is used. If nhandles is not specified, 1 handle is returned. (Note that if you specify nhandles, you must also specify a poolname.) If not enough handles are available to fulfill the request, it waits until they are available. You must request all the handles you will need for a specific pool with one call to ns_db gethandle. You must release all your database handles explicitly (with ns_db releasehandle) before acquiring more. If you request multiple handles from the database, this function returns a Tcl list of database handles (space delimited). In this case, each handle must be released with a separate call to ns_db releasehandle.

If a timeout is not specified or timeout is zero, ns_db gethandle will wait indefinitely (perhaps forever) for the requested number of handles to become available. If timeout is greater than zero, ns_db gethandle will either return with the handles within that time period, or return "" if the time period was exceeded, or generate a Tcl error of the form "could not allocate n handle(s) from pool 'poolname'. If timeout is less than zero, ns_db gethandle will not block. It will either return with the handles, or generate the above Tcl error. See the examples for ns_db gethandle, below.

ns_db getrow fetches the next row waiting to be retrieved after an ns_db select. The data is dumped right into the set associated with SETID, which should be the set returned by the ns_db select. It returns "1" if there are more rows waiting and returns "0" otherwise. If you call ns_db getrow again after already receiving "0" on the previous call, an error is returned.

ns_db open returns a handle at a lower level, circumventing the pools.

ns_db poolname returns the database pool that this handle came from.

ns_db pools returns a list of all database pools.

ns_db releasehandle puts the handle back in the pool. When your operation has finished running, the server will automatically return any handles to their pools, so you don't normally have to call this function.

ns_db 1row expects the SQL to be a select statement that returns exactly one row and returns that row as an ns_set.

ns_db 0or1row expects the SQL to be a select statement that returns exactly zero or one row. On zero rows, a null string is returned. On one row, a newly allocated ns_set is returned.

ns_db password returns the password of the user for the database pool.

ns_db select executes the SQL statement on the database server. It returns an ns_set with the keys set to the column names that were selected. Use ns_db getrow to retrieve rows. You cannot perform nested select statements. Before you start a new select statement, you must first either retrieve all the rows from the first select or use the ns_db flush statement to flush any rows not yet retrieved.

ns_db setexception returns the specified status code and message to the client.

ns_db sp_exec executes a stored procedure that has been initialized with ns_db sp_start and ns_db sp_setparam. It returns "NS_DML" if the command was succsesfully executed but did not return rows, or it returns "NS_ROWS" if the command was successfully executed and did return rows (which can then be fetched with ns_db bindrow and ns_db getrow). It throws an error if the command failed. This function is implemented only for the Sybase database driver. See the Examples section, below, for an example of this function.

ns_db sp_getparams gets any output parameters set after executing a stored procedure with ns_db sp_exec. It returns an ns_set or throws an error on failure. This function is implemented only for the Sybase database driver. See the Examples section, below, for an example of this function.

ns_db sp_returncode gets the return code from a stored procedure. It must be called after ns_db sp_exec. This function is implemented only for the Sybase database driver. See the Examples section, below, for an example of this function.

ns_db sp_setparam sets a parameter for a call to a stored procedure. The varname is the name of the variable, for example "@name". The vartype is the data type of this parameter, for example "varchar". The inout argument indicates whether it's an input or output parameter. It must be set to either "in" or "out". The value is the paramter value to send. This function returns 1 on success and throws an error on failure. This function is implemented only for the Sybase database driver. See the Examples section, below, for an example of this function.

ns_db sp_start begins execution of the stored procedure called procname. It returns 0 on success and throws an error on failure. This function is implemented only for the Sybase database driver. See the Examples section, below, for an example of this function.

ns_db user returns the user (as specified for the User parameter of the configuration file) for the database pool.

ns_db verbose changes the verbose setting (the Verbose parameter in the configuration file) for the database pool.

Examples

1. Here's an example ADP that runs a stored procedure called "p_TestProc" in a pool called "sybase":

       <HTML>
       <HEAD>
       </HEAD>
       
       <BODY>
       
       <%
       #
       # The new stored procedure commands that I've implemented are:
       #
       #   ns_db sp_start      $dbhandle $procname
       #   ns_db sp_setparam   $dbhandle $varname, $vartype, in|out, 
   $value
       #   ns_db sp_exec       $dbhandle
       #   ns_db sp_returncode $dbhandle
       #   ns_db sp_getparams  $dbhandle
       #
       # Look for them and their usage below...
       #
       
       set formdata [ns_conn form $conn]
       #set pool  [ns_set get $formdata "pool"]
       #set pool  "sybdoug"
       set pool "sybase"
       
       if {$pool == ""} {
           ns_puts "<P>No database pool specified.</P>"
           ns_adp_break
       }
       
       set db         [ns_db gethandle  $pool]
       set datasource [ns_db datasource $db]
       set dbtype     [ns_db dbtype     $db]
       set driver     [ns_db driver     $db]
       set poolname   [ns_db poolname   $db]
       set user       [ns_db user       $db]
       set password   [ns_db password   $db]
       
       #
       # Show some information about this connection to the database.
       #
       ns_puts "<TABLE>"
       ns_puts "<TR><TD>datasource</TD><TD>$datasource</TD></TR>"
       ns_puts "<TR><TD>dbtype</TD><TD>$dbtype</TD></TR>"
       ns_puts "<TR><TD>driver</TD><TD>$driver</TD></TR>"
       ns_puts "<TR><TD>poolname</TD><TD>$poolname</TD></TR>"
       ns_puts "<TR><TD>user</TD><TD>$user</TD></TR>"
       ns_puts "<TR><TD>password</TD><TD>$password</TD></TR>"
       ns_puts "</TABLE>"
       ns_puts "<BR><BR>"
       
       #
       # Turn on server tracing for this handle -- only do this if 
   you need debug
       # output on the server side.
       #
       ns_ext traceon $db "/tmp/sybtrace"
       
       #
       # Create a stored procedure.
       #
       ns_puts "<P>Calling ns_db sp_start...</P>"
       set ret [ns_db sp_start $db "p_TestProc"]
       ns_puts "<P>ns_db sp_start db p_TestProc returned $ret</P>"
       
       #
       # Set the parameters for this stored procedure.  The SQL definition
   of this
       # procedure is:
       #
       #   CREATE PROCEDURE p_TestProc(@x int, @y varchar(16) out, @z 
   int out)
       #
       # The arguments to ns_db sp_setparam are like this:
       #
       #   ns_db setparam $dbhandle $varname, $vartype, in|out, $value
       #
       set ret [ns_db sp_setparam $db "@x" int in 4]
       ns_puts "<P>ns_db sp_setparam @x returned $ret</P>"
       set ret [ns_db sp_setparam $db "@y" varchar out "varchar val"]
       ns_puts "<P>ns_db sp_setparam @y returned $ret</P>"
       set ret [ns_db sp_setparam $db "@z" int out 231]
       ns_puts "<P>ns_db sp_setparam @z returned $ret</P>"
       
       #
       # Execute the stored procedure now
       #
       set ret [ns_db sp_exec $db]
       ns_puts "<P>ns_db sp_exec returned $ret</P>"
       
       #
       # Bind an ns_set to the rows returned from this procedure
       #
       set row [ns_db bindrow $db]
       if {$row == ""} {
           ns_puts "<P>No row data returned from bindrow.</P>
           ns_adp_break
       }
       
       #
       # Display all of the rows returned in a generic way
       #
       set numcols [ns_set size $row]
       ns_puts "<TABLE BORDER>"
       ns_puts "<TR>"
       for {set i 0} {$i < $numcols} {incr i} {
           ns_puts "<TH>[ns_set key $row $i]</TH>"
       }
       while {[ns_db getrow $db $row]} {
           ns_puts "<TR>"
           for {set i 0} {$i < $numcols} {incr i} {
               ns_puts "<TD VALIGN=\"TOP\">[ns_set value $row $i]</TD>"
           }
           ns_puts "</TR>"
       }
       ns_puts "</TABLE>"
       
       #
       # Show the return code
       #
       ns_puts "<P>Return code: [ns_db sp_returncode $db]</P>"
       
       #
       # Process output parameters.  The output parameters are returned
   in an ns_set
       # with the keys set to the parameter names from the above setparam
   calls.
       # All of the parameters that were specified as an "out" parameter
   will be
       # represented here if they were defined as output values in 
   the stored
       # procedure itself.
       #
       catch {
           ns_puts "<P>Output parameters:</P>"
           set paramset [ns_db sp_getparams $db]
           if {$paramset == ""  || $paramset == 0} {
               ns_puts "<P>sp_getparams failed</P>"
           }
       } paramerr
       if {$paramerr != ""} {
           ns_puts "<P>getparams generated a database exception</P>"
           ns_adp_break;
       }
       
       #
       # Display the output parameters
       #
       set numparams [ns_set size $paramset]
       for {set i 0} {$i < $numcols} {incr i} {
           set key [ns_set key $paramset $i]
           ns_puts "<P>Param $key: [ns_set get $paramset $key]</P>"
       }
       %>
       
       </BODY>
       </HTML>
   

2. These are valid uses of ns_db gethandle:

       ns_db gethandle 
       # 1 handle from default pool
       ns_db gethandle -timeout 23 
       # 1 handle from default pool, 23 sec timeout
       ns_db gethandle -timeout -1 poolname
       # 1 handle from poolname, error if not available
       ns_db gethandle poolname 
       # 1 handle from poolname
       ns_db gethandle -timeout 23 poolname 
       # 1 handle from poolname, 23 sec timeout
       ns_db gethandle poolname 5            
       # 5 handles from poolname
       ns_db gethandle -timeout 23 poolname 5 
       # 5 handles from poolname, 23 sec timeout
   

This is not valid, because nhandles is specified without a poolname:

    ns_db gethandle 5 
    # it thinks 5 is the pool name