Reply to the tickets #2


  • New
  • Enhancment
Open
  • rautamiekka created this issue Apr 14, 2015

    What is the enhancement in mind? How should it look and feel?
    The plugin is quite useless since you can't reply to the tickets. Suggest §/ticket reply <#> <text>§ as the way.

    Please provide any additional information below.
    1) The table structure as given by MySQL 5.6.x §SHOW CREATE TABLE§, created by me with phpMyAdmin:

    CREATE TABLE `tickets_replies` (
     `TICKET_ID` mediumint(8) unsigned NOT NULL,
     `REPLY_ID` int(10) unsigned NOT NULL AUTO_INCREMENT,
     `UUID` varchar(40) CHARACTER SET ascii COLLATE ascii_bin DEFAULT NULL,
     `DATE` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
     `REPLY` longtext COLLATE utf8mb4_unicode_ci NOT NULL,
     PRIMARY KEY (`REPLY_ID`),
     KEY `TICKET_ID` (`TICKET_ID`),
     KEY `UUID` (`UUID`),
     CONSTRAINT `fk_tickets_replies_TICKET_ID` FOREIGN KEY (`TICKET_ID`) REFERENCES `tickets` (`TICKET_ID`) ON DELETE CASCADE ON UPDATE CASCADE
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci
    

    2) The MySQL table and SQLite db needs to be full UTF8 (called 'utf8mb4' in MySQL'). Same for connections.

    3) Described in the above code, recommend using foreign key constraints (InnoDB required on MySQL; MyISAM sucks anyway) where §tickets_replies.TICKET_ID§ references §tickets.TICKET_ID§ (

    ON DELETE CASCADE
    ON UPDATE CASCADE
    

    ) where
    - §ON DELETE CASCADE§=delete all replies relating to the ticket which is being deleted from §tickets§
    - §ON UPDATE CASCADE§=update §TICKET_ID§ in §tickets_replies§ to the number that §tickets§ received for a ticket.

  • rautamiekka added the tags New Enhancment Apr 14, 2015

To post a comment, please login or register a new account.