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

--- Comment #6 from Nick Clemens <n...@bywatersolutions.com> ---
(In reply to Martin Renvoize from comment #5)
> I think the defined check is there so we don't trigger warnings in the
> comparison...  shouldn't we attempt to fix this at the import script level?

I think they will both always have all of the columns:
- the db object has them because of schema
- the incoming object has them all because we fill everything found in
set_column_keys

Testing I don't see errors from this new code

I do get an unrelated warn before and after the patch:
[2024/03/05 18:40:18] [WARN] Use of uninitialized value within %csvkeycol in
array element at /kohadevbox/koha/Koha/Patrons/Import.pm line 288, <$fh> line
2.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
https://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