Subversion Repositories SmartDukaan

Last modification

• Rev 37599 2026-09-11 20:09:50
• Author: amit

• Log message:

  Reuse the managed snapshot row in the sweep instead of building a second instance
  
  Every sweep after the first failed with 'A different object with the same
  identifier value was already associated with the session :
  PartnerInvestment#107198' and wrote nothing.
  
  selectByFofoIds returns managed entities. The loop then constructed a fresh
  PartnerInvestment for the same id and called saveOrUpdate on it, which Hibernate
  rejects. Sweep one survived only because the table was empty, so no row was
  managed - the failure could not appear until a second run.
  
  Now mutates the row already in the session when there is one, falling back to a
  new instance only for partners with no snapshot. The previous base and gross stock
  are captured before mutation, since comparing the row against itself afterwards
  would report nothing as ever changed.
  
  persist() is kept: a no-op for the managed rows (dirty checking flushes them), and
  still the INSERT for partners appearing between sweeps.
  
  Drops baseDiffersFrom(), now unused - the comparison is against the captured prior
  value, still rounded to paise by the setter on both sides.