[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Double jeopardy when a NO-UNDO temp table violates a uniqueness constraint

Status
Not open for further replies.
D

dbeavon

Guest
The "EMPTY TEMP-TABLE" operation always raises its own error again (although I don't see why it should when "delete tt" does not). The fact that I can't seem to avoid the raising of the error is the problem. I'm tempted to open a support case. It would seem to me that an "EMPTY TEMP-TABLE" operation should supercede and trump all the constraint violations that might otherwise exist in the default buffer. Those should be a moot point if the data is being cleared. Alternatively there should be a command to remove or disable the constraints in the current TT or DS. That is something I was hoping to find in the list of temp-table handle operations...

Continue reading...
 
Status
Not open for further replies.
Top