I don't believe that Navicat has that ability.
Assuming that you have a MySQLdump (text-based backup) of the old data, do a GREP for INSERT, and for (either INVENTORY, or PLAYER_CORPSES, and for the char_id of that specific player) -- case insensitive.
If you don't have a text backup, then if you do have binary logging enabled, then the old data could still be in the binlogs. Check to see the date-time of the binlogs. Do (for instance) a mysqlbinlog binlog.000001 > new-backup.sql and see if the data might still be in there and you may be able to grep that. Of course, that would only have the current inserts/deletes for the database from the time you last purged the logs, up to the expire dates (if you have binlogs).
Then manually delete the current rows from those tables for that char-id and re-insert those GREPped versions.
I have a trigger on player_corpses and on inventory (on update, insert and delete) so it inserts into an auditing table (called aud_player_corpses and aud_inventory) with just char_id, slot_id, item_id, charges and _when (date-time stamp. Anything older than 90 days is deleted from the audit tables. But I can go back to any point in time with the audit-tables.
|