Ticket #3925 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

Upgrade does not alter eprint__rindex table

Reported by: tmb Owned by:
Priority: Customer Report Milestone: 3.2.5
Component: DB Version: 3.2
Severity: normal Keywords:
Cc:

Description

Local 3.2.4 clean install:

CREATE TABLE `eprint__rindex` (
  `field` varchar(64) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
  `word` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
  `eprintid` int(11) NOT NULL,
  PRIMARY KEY (`field`,`word`,`eprintid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8

Upgraded from 3.1:

CREATE TABLE `eprint__rindex` (
  `eprintid` int(11) NOT NULL DEFAULT '0',
  `field` varchar(64) NOT NULL DEFAULT '',
  `word` varchar(128) NOT NULL DEFAULT '',
  PRIMARY KEY (`field`,`word`,`eprintid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 

This causes problems with indexing as the rindex is still case-insensitive eg:

DBD::mysql::st execute failed: Duplicate entry '_fulltext_-FOUR-108' for key 'PRIMARY' at /opt/eprints3/perl_lib/EPrints/Database.pm line 1298, <DATA> line 151.

(where fulltext "four" had already been rindexed for the same item).

Change History

Changed 4 years ago by tdb01r

  • status changed from new to closed
  • resolution set to fixed

Resolved by r6127.

Note: See TracTickets for help on using tickets.