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

  • Thread starter Thread starter frank.meulblok
  • Start date Start date
Status
Not open for further replies.
F

frank.meulblok

Guest
[quote user="dbeavon"] Deleting the default record buffer in a catch block is also a very questionable workaround... especially if you are doing it in a generic catch block ... in an outer scope that is not supposed to know about the internal implementation details of any methods that are called. [/quote] Any questionable side effects you risk introducing can be contained by keeping the CREATE in it's own DO block with it's own catch. That's pretty much the only way to be certain which buffer you need to delete the record from, and to get rid of the problematic record before any other code can run into it. Kind of a pain to make sure that's done everywhere though, and your code won't look any cleaner/more readable either.

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