| [Top] | [Contents] | [Index] | [ ? ] |
This manual is for osdbi, version 0.0.0.
| 1. Introduction | ||
| 2. Interface Functions | Interface functions. | |
| Function Index |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The source resides in a git repository at http://www.cs.berkeley.edu/~ejr/gits/osdbi.git/ and as occasional snapshots at http://www.cs.berkeley.edu/~ejr/dev/octave/osdbi/ .
The most recent snapshot as of 12 March, 2008 is http://www.cs.berkeley.edu/~ejr/dev/octave/osdbi/osdbi-0.0.0.tar.gz and is in package format, see See Octave package: (octave3.0)Packages.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Make a new connection through driver drivername. Parameters can be passed by optional key strings and val values. If given an existing connection, the returned conn is a new, cloned connection to the original data source if possible.
|
Set options on connection conn. The returned errcode is zero on success. Other values are driver-dependent.
|
Opens the connection. A zero errcode signals success; other values are driver-dependent.
Closes the connection.
Returns true if the connection is open.
Returns true if the connection is read-only.
Returns true if the connection is in a good (non-error) state. The exact meaning is driver-dependent, but it is reasonable to assume that a non-"ok" connection should be closed. It may be possible to generate an "ok" connection by cloning the non-"ok" connection.
Returns the driver name.
Returns a string containing a driver-dependent description of the connection intended for end-user consumption.
Returns a string containing a driver-dependent description of the connection intended for end-user consumption.
Insert scalar structure data into table tablename on connection conn. The fieldnames are used as column names. Each field should contain an array or cell array of values. If a field is scalar, it is replicated to match any array fields. An empty field is treated as a null. All array fields must be of the same length. The returned errcode will be zero on success. Data is inserted in a single transaction, so either all the data is inserted or none is.
The optional structure outfields or list of strings outname specify fields to return from the recently inserted data. These can be used to retrieve autoincrement id fields or other generated key data.
On success the return value will depend on the number of requested columns and their types. Multiple columns will be returned in a structure. A single column will be returned as either a Cell column or, if possible, downcasted to a numerical column which may in turn be narrowed to a scalar.
On error, the return value will be a scalar error code which may be indistinguishable from actual data. However, an error is signaled through the common Octave mechanism. A try block or an eval is recommended to detect errors.
|
See also: osdbi_expand.
An arbitrary superfunction. Parameters are bound by position. Results are narrowed when possible.
|
See also: osdbi_insert,osdbi_expand.
Expands the structure array indata with data from table table through. DB connection conn. Each structure array entry provides a pattern of values to match to values in table. The fieldnames are used as column names. The result is the distinct union of all the matching rows. Empty fields are wildcards.
Output fields can be limited either by the fieldnames of outfields or by string names. The result is a structure on success and either a scalar error code or an empty matrix on failure.
Currently NULLs are translated to Octave's NA.
|
See also: osdbi_insert.
Turn on tracing. The exact effects depend on the driver.
Returns true if tracing. The exact effects of tracing depend on the driver.
Internal connection creator. Call via osdbi.
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| Jump to: | O |
|---|
| Jump to: | O |
|---|
| [Top] | [Contents] | [Index] | [ ? ] |
| [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by Jason Riedy on March, 12 2008 using texi2html 1.78.
The buttons in the navigation panels have the following meaning:
| Button | Name | Go to | From 1.2.3 go to |
|---|---|---|---|
| [ < ] | Back | Previous section in reading order | 1.2.2 |
| [ > ] | Forward | Next section in reading order | 1.2.4 |
| [ << ] | FastBack | Beginning of this chapter or previous chapter | 1 |
| [ Up ] | Up | Up section | 1.2 |
| [ >> ] | FastForward | Next chapter | 2 |
| [Top] | Top | Cover (top) of document | |
| [Contents] | Contents | Table of contents | |
| [Index] | Index | Index | |
| [ ? ] | About | About (help) |
where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure:
This document was generated by Jason Riedy on March, 12 2008 using texi2html 1.78.