https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17234
--- Comment #9 from Blou <[email protected]> --- (In reply to M. Tompsett from comment #4) > > + `type` ENUM('', 'string', 'date', 'number', 'boolean', 'sum') > > NOT NULL COMMENT 'what type of data this holds, relevant when storing it in > > the search engine', > > I haven't looked yet, but this seems like a bad solution. Invalid entries in > the ENUM column are likely caused by applying patches that didn't get into > master. I may get around to looking further, but this patch portion doesn't > seem right to me. Maybe I shouldn't have mixed the two patches. But both issues prevent me from completing updatedatabase.pl with mysql 5.7, related to its stringent requirements. That said, the entries in admin/searchengine/elasticsearch/mappings.yaml specify '' as type. So this to fix updatedatabase, there are two options: 1) correct a few (hundreds?) entries in mappings.yaml, knowing what you're doing with elastic search. 2) allow for empty types. NOTE: there are more blockers. More small patches coming. -- 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/
