Kbase P65784: For Oracle DataServer, would it be a good standard to perform the validate after all creates?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/19/2008 |
|
Status: Verified
GOAL:
For Oracle DataServer, would it be a good standard to perform the validate after all creates?
GOAL:
For SQL server DataServer, would it be a good standard to perform the validate after all creates?
GOAL:
Why can't I find the record I just created if I don't validate?
GOAL:
We have logic that performs a find on the record before end of transaction. The record then is not available. To prevent this, would it be a good standard to always validate it?
FACT(s) (Environment):
Oracle DataServer
ODBC DataServer
MS SQL DataServer
All Supported Operating Systems
Progress 8.x
Progress 9.x
OpenEdge 10.x
FIX:
Yes, that is the purpose of validate statement.
Because DataServer for Oracle (MS SQL server, ODBC) writes the record later than Progress does, if you perform a find right after record creation, you might not be able to find the record because it has not yet written the record to the database. To get the correct response from the DataServer, use validate. Using validate statement causes the DataServer to write the record to the database before the FIND statement occurs.