SQLCNVER parameter: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
|||
| Line 11: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 | <dd><var class="product">Model 204 V3.1</var> | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>The processing procedure the SQL Server follows when it finds dirty data during an SQL retrieval or update</p> | <p>The processing procedure the SQL Server follows when it finds dirty data during an SQL retrieval or update</p> | ||
Revision as of 10:28, 7 September 2017
SQL fetch option
Summary
- Default value
- 0
- Parameter type
- User
- Where set
- On User 0's or on user's parameter line
- Related products
- All
- Introduced
- Model 204 V3.1
Description
The processing procedure the SQL Server follows when it finds dirty data during an SQL retrieval or update
Dirty data is Model 204 file data that the Model 204 SQL Server cannot convert to the SQL data type you specify. The SQLCNVER parameter tells the SQL Server what to do if it finds dirty data during an SQL retrieval or update. SQLCNVER, specified with the User 0 parameters or on the first IODEV line, has two settings:
| Setting | Meaning |
|---|---|
| 0 | Stop processing the SQL request and return a negative SQL code if dirty data is encountered. |
| 1 | Skip any row with dirty data and continue processing the SQL request. Include a warning message with returned data. |
Regardless of the SQLCNVER setting, the SQL Server writes a message to the audit trail whenever dirty data is encountered during an SQL retrieval or update. The message (number 1296) lists the Model 204 file, field, and record number of the record with the dirty data.