[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Duplicate index error on TT from unrelated procedure

  • Thread starter Thread starter jbijker
  • Start date Start date
Status
Not open for further replies.
J

jbijker

Guest
Well you have 2 options: 1. Remove the "NO-UNDO" from the TT definition - i.e. in the event of an error / rollback it will remove the offending record for you. However it does have a performance implication because OE now needs to store all changes to the TT when you're inside a transaction block. 2. Change the Primary Index to a non-unique index. Personally I see no need of having a primary index on a TT. This has bitten me a couple of times. I'm using #2 above. If you really need to enforce uniqueness you can always do so by doing a FIND FIRST to check if a record is already there.

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