Installation guide

7. mxODBC Cursor Objects
.connection
Connection object on which the cursor operates.
.converter
Read-only access to the converter function set using the
cursor.setconverter()method or inherited from the
connection.converter attribute at cursor creation time.
The attribute is
None in case no converter function was set or inherited.
mxODBC will then use the default type conversions when fetching data from
the database. See section 8.5 Output Conversions for details.
.cursortype
Read/write attribute that sets the ODBC cursor type this cursor. It takes the
same values as the
connection.cursortype instance variable and defaults to
the creating connection object's settings for
connection.cursortype. For
possible values, please see the connection
.cursortype attribute in section
6.8 Connection Object Attributes.
Changes to the cursor type must be made before opening the cursor, ie. before
executing a statement on it.
Please refer to section 5.8 ODBC Cursor Types for more details on cursor
types.
.datetimeformat
Attribute to set the output format for date/time/timestamp columns on a per
cursor basis. It takes the same values as the
connection.datetimeformat
instance variable and defaults to the creating connection object's settings for
connection.datetimeformat.
.decimalformat
Attribute to set the output format for decimal/numeric columns on a per cursor
basis. It takes the same values as the
connection.decimalformat instance
variable and defaults to the creating connection object's settings for
connection.decimalformat.
.description
This read-only attribute is a sequence of 7-item sequences for operations that
produce a result set (which may be empty).
Each of these sequences contains information describing one result column:
(name, type_code, display_size, internal_size, precision,
scale, null_ok)
.
This attribute will be
None for operations that do not return rows or if the
cursor has not had an operation invoked via the
.execute*() method yet.
mxODBC always returns None for
display_size and internal_size. This
information can be obtained via
connection.gettypeinfo(), if needed.
The
type_code can be interpreted by comparing it to the type objects
specified in the section 8 Type Objects and Constructors
below. mxODBC
returns the SQL type integers in this field. These are described in the section 8
135