dbUnit / Bugs / #424 CachedDataSet does not work

#424 CachedDataSet does not work

Milestone: v2.6.*

Status: closed-fixed

Owner: Hans Deragon

Labels: CachedDataSet (1)

Fixed Release: 2.7.0

Priority: 5

Updated: 2020-02-23

Created: 2019-02-28

Creator: Anghel Botos

Private: No

CachedDataSet was broken by a refactoring commit. Please refer to this comment from me on the offending commit.

BR,
Anghel

Discussion

Jeff Jensen - 2019-03-01

Ticket moved from /p/dbunit/feature-requests/223/

Can't be converted:

_milestone: 2.6.1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeff Jensen - 2019-03-01

status: open --> pending

Fixed Release: --> (not fixed)

Found Release: 2.6.1 --> v2.6.*
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeff Jensen - 2019-03-01

Thanks for reporting. Since you understand the issue well, would apprecite if you would create reproducing tests and a fix; are you ok to, please? If so, an attached patch or a merge request - whichever is easiest for you.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeff Jensen - 2019-03-02

assigned_to: Hans Deragon

Fixed Release: (not fixed) --> 2.6.1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Hans Deragon - 2019-03-08

Branch FixCachedDataSet contains the fix and a unit test ensuring it is working well. It will be merged in the next release, 2.6.1.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Hans Deragon - 2019-03-30

@jeff, you have been writting to me emails and the way you are writting suggest that you never getting my emails. Check you spam folder please.

Following, the content of my last emails regarding this bug report. The bug fix is ready for merge; all has been reviewed.

*I created branch FixCachedDataSetDeragonDev. So now you have two branches for the fix, identical in all ways except for the name of the main developer in the changes.xml file; the first one, FixCachedDataSet is set to you and due-to me, the other, FixCachedDataSetDeragonDev makes only reference to me.

You choose which branch to merge and then delete both.*

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Jeff Jensen - 2019-03-30
  
  Thanks Hans, I have received no emails from you since March 5. Nothing in spam.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeff Jensen - 2019-03-31

status: pending --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.