当我从Mirth Connect Server
mysql> describe OLD_MESSAGE;
+---------------------------+--------------+------+-----+-------------------+-----------------------------+
| Field | Type | Null | Key | Default | Extra |
+---------------------------+--------------+------+-----+-------------------+-----------------------------+
| SEQUENCE_ID | int(11) | NO | PRI | NULL | auto_increment |
| ID | char(36) | NO | UNI | NULL | |
| SERVER_ID | char(36) | NO | | NULL | |
| CHANNEL_ID | char(36) | NO | MUL | NULL | |
| SOURCE | varchar(255) | YES | | NULL | |
| TYPE | varchar(255) | YES | | NULL | |
| DATE_CREATED | timestamp | NO | | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP |
| VERSION | varchar(40) | YES | | NULL | |
| IS_ENCRYPTED | smallint(6) | NO | | NULL | |
| STATUS | varchar(40) | YES | | NULL | |
| RAW_DATA | longtext | YES | | NULL | |
| RAW_DATA_PROTOCOL | varchar(40) | YES | | NULL | |
| TRANSFORMED_DATA | longtext | YES | | NULL | |
| TRANSFORMED_DATA_PROTOCOL | varchar(40) | YES | | NULL | |
| ENCODED_DATA | longtext | YES | | NULL | |
| ENCODED_DATA_PROTOCOL | varchar(40) | YES | | NULL | |
| CONNECTOR_MAP | longtext | YES | | NULL | |
| CHANNEL_MAP | longtext | YES | | NULL | |
| RESPONSE_MAP | longtext | YES | | NULL | |
| CONNECTOR_NAME | varchar(255) | YES | | NULL | |
| ERRORS | longtext | YES | | NULL | |
| CORRELATION_ID | varchar(255) | YES | MUL | NULL | |
| ATTACHMENT | smallint(6) | YES | MUL | NULL | |
+---------------------------+--------------+------+-----+-------------------+-----------------------------+
23 rows in set (0.05 sec)
最佳答案
最后,我用相同的数据建立了另一个Mirth Connect服务器,并测试删除旧的_消息表。结果发现,在丢掉那张桌子后,我没有任何不良反应。我希望这能帮助别人!
关于mysql - Mirth Connect-升级到版本3后,删除old_messages表是否安全?,我们在Stack Overflow上找到一个类似的问题:https://stackoverflow.com/questions/28573486/