class QSql#

The QSql namespace contains miscellaneous identifiers used throughout the Qt SQL module. More

Note

This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE

Detailed Description#

See also

Qt SQL

class Location#

This enum type describes special SQL navigation locations:

Constant

Description

QSql.BeforeFirstRow

Before the first record.

QSql.AfterLastRow

After the last record.

See also

at()

class ParamTypeFlag#

(inherits enum.Flag) This enum is used to specify the type of a bind parameter.

Constant

Description

QSql.In

The bind parameter is used to put data into the database.

QSql.Out

The bind parameter is used to receive data from the database.

QSql.InOut

The bind parameter is used to put data into the database; it will be overwritten with output data on executing a query.

QSql.Binary

This must be OR’d with one of the other flags if you want to indicate that the data being transferred is raw binary data.

class TableType#

This enum type describes types of SQL tables.

Constant

Description

QSql.Tables

All the tables visible to the user.

QSql.SystemTables

Internal tables used by the database.

QSql.Views

All the views visible to the user.

QSql.AllTables

All of the above.

class NumericalPrecisionPolicy#

Numerical values in a database can have precisions greater than their corresponding C++ types. This enum lists the policies for representing such values in the application.

Constant

Description

QSql.LowPrecisionInt32

Force 32bit integer values. In case of floating point numbers, the fractional part is silently discarded.

QSql.LowPrecisionInt64

Force 64bit integer values. In case of floating point numbers, the fractional part is silently discarded.

QSql.LowPrecisionDouble

Force double values. This is the default policy.

QSql.HighPrecision

Strings will be used to preserve precision.

Note: The actual behaviour if an overflow occurs is driver specific. The Oracle database just returns an error in this case.