https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23151

--- Comment #45 from Jonathan Druart <[email protected]> 
---
(In reply to Kyle M Hall from comment #29)
> (In reply to Jonathan Druart from comment #28)
> > (In reply to Jonathan Druart from comment #20)
> > > However the column need to be set for existing installations.
> > 
> > Still valid, I do not think we should push it without updating the existing
> > entries.
> 
> I don't believe this update is even possible given we don't have the data
> we'd need to fix it, and if we did we wouldn't have this bug to begin with ;)
> 
> In addition, this is a serious problem that is happening *now*. I think we
> need to get this patched post-haste and we can solve this db update issue on
> followup report. Right now libraries are losing data that they wouldn't not
> have lost if this hadn't been set to failed qa.

% git checkout before these patches
% Create patron's modifications
% git checkout master
% Approve the patron's modifications
=> The modifications are lost.

So we replaced a data lost, with another...

That's why I was insisting.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to