AuroraMiddleware/qt5base-lts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

QtSql: Correct documented default precision policy.

Browse Source 
Follow-up to commit c9f77564df14f91276e9ca693a9b3f339dab9334
Task-number: QTBUG-27482

Change-Id: I17c12ee14d4609bccbe67bba2581f13d72c069ae
Reviewed-by: Mark Brand <mabrand@mabrand.nl>
This commit is contained in:
Mark Brand 2012-10-13 23:10:27 +02:00 committed by The Qt Project
parent 3e030a9652
commit 7a34e88edc
1 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/sql/kernel/qsql.qdoc
View File

@ -81,19 +81,15 @@
/*!
\enum QSql::NumericalPrecisionPolicy
This enum type describes at which precision levels numerical values are read from
a database.
Some databases support numerical values with a precision that is not storable in a
C++ basic data type. The default behavior is to bind these values as a QString.
This enum can be used to override this behavior.
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.
\value LowPrecisionInt32 Force 32bit integer values. In case of floating point numbers,
the fractional part is silently discarded.
\value LowPrecisionInt64 Force 64bit integer values. In case of floating point numbers,
the fractional part is silently discarded.
\value LowPrecisionDouble Force \c double values.
\value HighPrecision The default behavior - try to preserve maximum precision.
\value LowPrecisionDouble Force \c double values. This is the default policy.
\value 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.