Bug 13539: Remove unused table patroncards
It appears that the table patroncards hasn't been used since the database updates for the rewritten label modules ('3.01.00.107'). It's time to remove them from the database. As the patron card batches were needed for printing and the data has not been accessible in a long time, it seems safe to delete it. Signed-off-by: Brendan Gallagher <brendan@bywatersolutions.com> Signed-off-by: Jonathan Druart <jonathan.druart@biblibre.com> Signed-off-by: Tomas Cohen Arazi <tomascohen@gmail.com>
This commit is contained in:
parent
0d31fca4f1
commit
b161f4fbc7
2 changed files with 7 additions and 15 deletions
|
@ -1712,21 +1712,6 @@ CREATE TABLE `overduerules` ( -- overdue notice status and triggers
|
|||
PRIMARY KEY (`branchcode`,`categorycode`)
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
|
||||
|
||||
--
|
||||
-- Table structure for table `patroncards`
|
||||
--
|
||||
|
||||
DROP TABLE IF EXISTS `patroncards`;
|
||||
CREATE TABLE `patroncards` (
|
||||
`cardid` int(11) NOT NULL auto_increment,
|
||||
`batch_id` varchar(10) NOT NULL default '1',
|
||||
`borrowernumber` int(11) NOT NULL,
|
||||
`timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
|
||||
PRIMARY KEY (`cardid`),
|
||||
KEY `patroncards_ibfk_1` (`borrowernumber`),
|
||||
CONSTRAINT `patroncards_ibfk_1` FOREIGN KEY (`borrowernumber`) REFERENCES `borrowers` (`borrowernumber`) ON DELETE CASCADE ON UPDATE CASCADE
|
||||
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
|
||||
|
||||
--
|
||||
-- Table structure for table `patronimage`
|
||||
--
|
||||
|
|
|
@ -10018,6 +10018,13 @@ if ( CheckVersion($DBversion) ) {
|
|||
SetVersion ($DBversion);
|
||||
}
|
||||
|
||||
$DBversion = "3.19.00.XXX";
|
||||
if ( CheckVersion($DBversion) ) {
|
||||
$dbh->do(qq|DROP table patroncards;|);
|
||||
print "Upgrade to $DBversion done (Bug 13539: Remove table patroncards from database as it's no longer in use)\n";
|
||||
SetVersion ($DBversion);
|
||||
}
|
||||
|
||||
# DEVELOPER PROCESS, search for anything to execute in the db_update directory
|
||||
# SEE bug 13068
|
||||
# if there is anything in the atomicupdate, read and execute it.
|
||||
|
|
Loading…
Reference in a new issue