Changes between Initial Version and Version 1 of Ticket #2027


Ignore:
Timestamp:
Mar 18, 2019, 10:41:35 AM (5 years ago)
Author:
Bang Pham Huu
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2027

    • Property Summary petascope_investigate about @Transactional in Hibernate with auto flushpetascope_read coverage object from database for updating without cache
  • Ticket #2027 – Description

    initial v1  
    1 For example, if 1 coverage is read from database to be updated but in the meantime, the update handler throws exception. Hibernate still persist this half-updated coverage to database as it checks this object is dirty.
     1Currently, when petascope reads coverage object from database, it caches this object to be reused later (e.g: for `DescribeCoverage`). However, this makes a problem with updating coverage, when an error happens, coverage object also updated and returns an incorrect result (e.g: geo axis increases bounds) as the data cannot update yet.